Overview

Performance tuning an application is time consuming, and expensive. Useful tests often need dedicated hardware to run on. It's specialised and time consuming to prepare the ground work and write the various fixtures needed to run, and whose only perceived benefit is preventing a production issue that you don't even know will happen yet.

Stereotypical Scenarios and Outcomes

Here's some stereotypes I've encountered:

Due to a lack of examples on the Internet, I've created a basic Maven project that combines a custom sampler with the Maven plugin.

The sampler sleeps for 100ms, which is reported by the Lazerycode JMeter plugin.

You can find it on Github.

Here's the basic layout for a JMeter performance test using Cargo and Tomcat.

I'm currently reading Java Performance by Charlie Hunt and Binu John. It's a book that covers various aspects of Java specific performance testing. I wanted to test some of the approaches in the book, so I created an app on Github that has a series of problems. Without looking at the code, can you identify the performance problems?