Took a look at Locust before and did not find it as useful or generic as ApacheBench or Httperf (by HP). Locust felt a little too cutesy and high-level for most of the work I wanted to do - which was pretty simple.

Furthermore there were a lot of timing inaccuracies between the same test runs. It certainly could have been a fault in our code, but ab and Httperf seemed to give a lot more reliable and useful timing information. And they are just simpler to use. For one, not being browserbased can be nice when you are trying to iterate quickly.

Not trying to sell anyone against Locust, but at the least, I recommend you take a look at ab and Httperf to make sure you don't need something a whole lot simpler.

If you're using ab or httpperf, you should also take a look at wrk (https://github.com/wg/wrk). It can generate significant amount of load and has support for Lua scripting for request generation, response processing and reporting.

There is another fork of it (https://github.com/giltene/wrk2) which can be used if you want test at a consistent RPS.