How to Generate Millions of HTTP Requests (2012)
dak1n1.com
dak1n1.com
Incidentally, I've not read the linked article, but skimmed the first few paragraphs. The numbers of requests per second that he was able to generate with various tools seem remarkably low. ApacheBench is the least performant load generator since it's only single-threaded, but it can generate tens of thousands (about 25,000) requests per second on a i7 desktop machine. Wrk can generate significantly more since it uses all CPU cores of the load-generation machine.
The only thing missing would be an out-of-box solution for distributed load generation, which I believe is being developed. But today, you can use a 'scale-out' approach[2] which gives you the ability to combine the data from multiple Gatling instances into a single report, but as a post-process step.
[1] http://gatling.io [2] http://gatling.io/docs/2.1.5/cookbook/scaling_out.html
Does anyone know of an alternative that uses a pay-per-use option? In the meantime I have reverted to Bees with machine guns.
If the # of ports is the bottle neck, you can configure more IPs on a single host.
StormForger (https://stormforger.com) is cloud based Load Testing as a Service.
If you like to create test cases using a JavaScript DSL, run load tests and performance analysis and let us take care of all the provisioning and data analysis stuff: feel free to sign up for our private beta. Just drop us a line if you have further technical questions.
Talking about big numbers in this thread you may want to read this thread as well: https://news.ycombinator.com/item?id=7920930
There is a warning in the configuration file against using keep-alive with no explanation as to why. That makes it useless when you need to benchmark persistent connections.
Each Siege "user" (i.e. client) has it's own thread, which means they consume a large number of resources. Depending on your CPU, you will also hit a point where more time is spent switching between threads than actually sending requests. I wasn't able to exceed 400 users on my 2011 test machine. That makes it useless when you need to benchmark large numbers of connections.