Hi Miro,
As Gregory pointed, you should use a web-benchmark tool rather than rolling your own (e.g., weighttp).
If you intend to run benchmarks and play with many parameters, I'd recommend to use a framework to handle the experiments (I'm selling my magic potion here :P). I've wrapped the weighttp client to benchmark the mighty web servers in these Laborantin experiments:
-
https://github.com/lucasdicioccio/laborantin-bench-webFrom the results I got on my server, mighty handles from ~8K req/s to ~50K req/s depending on the input parameters of the server and of the measuring client. I'm not bragging that my server is beefy, but I report these results to show that results vary a lot with the methodology. Hence, take care and explore many operating points =).
Feel free to contribute a Scotty / Warp wrapper (or wait until I find time to make these myself).
Gregory, thanks for the -A4M tip, I wasn't aware of it. I'll patch my experiments with an extra parameter too =).