natural wrote:What are the most-common bottlenecks that eValid identifes in server loading runs?
That's hard to say, because almost every situation is different of course.
But there do seem to be patterns. Sometimes it is something obvious, about not realizing how BIG a sequence of pages is and inadvertantly saturating the primary input/output channel. Or being fooled by the sometimes "too intelligent" behavior of a load balancer. Or forgetting to set the maximum number of parallel sessions allowed by a back-end database engine to a large enough number.
It's funny, sometimes:
When you find a problem it almost always is in the last place you looked! Our advice is to keep on looking!
eValid Support