Beyond Performance Testing by:

So you found an odd pattern in your scatter chart that appears to be a bottleneck. What do you do now? How do you gather enough information to refute the inevitable response, “The application is fine, your tool/test is wrong”? And how do you present that information conclusively up front so you can get right down to working collaboratively with the development team to solve the problem? Those are the questions we’ll be addressing in this article. In addition, I’ll be giving you eight rules about bottlenecks that I’ve found to be both significant and useful during my tenure as a performance test engineer. This kicks off a four-article theme I call “finding bottlenecks to tune.” We’ve already explored the entry-level analysis that points us in the direction of a bottleneck or failure, and I’ve given some hints on how to ferret them out. Now it’s time to get under the hood. By the conclusion of Part 10, you should be confident in your ability to work with the development team to identify and exploit these areas of concern in a wa