I’ve used JMeter extensively to do performance and scalability tests for services I’ve helped build. Driving it through CI is almost essential in order to keep a reliable shared history of test runs. The jmeter-ec2 project has been helpful for scaling tests out economically, although it has significant bugs and limitations. I’ve usually measured the applications under test with New Relic.
There’s a practical limit per node that is somewhere between 200-4000 threads, which are a good proxy for individual users, depending on how JMeter is tuned. You can use multiple nodes to horizontally scale out though. I’ve done practical tests with the equivalent of 20,000 users using jmeter-ec2, spread across dozens of EC2 servers.
I’ve used JMeter extensively to do performance and scalability tests for services I’ve helped build. Driving it through CI is almost essential in order to keep a reliable shared history of test runs. The jmeter-ec2 project has been helpful for scaling tests out economically, although it has significant bugs and limitations. I’ve usually measured the applications under test with New Relic.
Is there a limit of how many users JMeter can simulate?
There’s a practical limit per node that is somewhere between 200-4000 threads, which are a good proxy for individual users, depending on how JMeter is tuned. You can use multiple nodes to horizontally scale out though. I’ve done practical tests with the equivalent of 20,000 users using jmeter-ec2, spread across dozens of EC2 servers.