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.<p>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.<p>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.
Used it for some substantial loadtesting, loved it.
It's real advantage compared to AB, siege, etc, is how easy it makes it to simulate real user interactions, not just mash on a few endpoints.
Only flaw in my books is the crazy high ulimit you need for simulating high numbers of unique actors. The easy clustering mitigates this though.
Shameless self promotion - I just wrote up a little doc [1] on using Locust and Kubernetes to run and scale distributed load tests along with some sample code [2].<p>I looked at JMeter and Gatling as alternatives but they were either a bit clunky (JMeter) or not distributed out of the box (Gatling). Late in the game I did discover Tsung (Erlang) but didn't get time to try it out - looks pretty powerful though.<p>[1] <a href="https://cloud.google.com/solutions/distributed-load-testing-using-kubernetes" rel="nofollow">https://cloud.google.com/solutions/distributed-load-testing-...</a><p>[2] <a href="https://github.com/GoogleCloudPlatform/distributed-load-testing-using-kubernetes" rel="nofollow">https://github.com/GoogleCloudPlatform/distributed-load-test...</a>
I used locust to supplement testing that third party was doing (they used some ibm product that I didn't have a license too).<p>I liked locust because it was easy to start using, but you write a decent amount of code if you have a complex application. I suggest using pyquery (<a href="https://pypi.python.org/pypi/pyquery" rel="nofollow">https://pypi.python.org/pypi/pyquery</a>) with it if you need to inspect any html, it was quite useful
Locust is a great tool. We use it to loadtest our websites and even a single Mac can make huge traffic. If somebody is interested in a highly optimized Vagrant VM for loadtesting and Locust (it's possible through a VM, but not exorbitant high loadtesting) check out this url <a href="https://github.com/PyBossa/loadtesting" rel="nofollow">https://github.com/PyBossa/loadtesting</a>
My fave locust setup is spinning up aws instances to tests from time to time. I've created ansible automation to help on that (<a href="https://github.com/gleicon/locust-swarm" rel="nofollow">https://github.com/gleicon/locust-swarm</a>) but it can be done manually. I still look on how to make it run casper.js tests but I think it would interfere with locust's performance.
A bit tongue in cheek, but is a testimonial from someone at EA/Dice something you'd want to highlight? I know Battlefield 4 is almost two years old at this point, but man, I still have the scars from that game...<p>In all seriousness, definitely going to check this out, not enough load testing is done at the company I work for, plus I want to learn more python.
So from what I understand this stands somewhere between as complex as Apache Bench and something as simple as Seige? I've had very little success with the former since its scripts are massive XML files and the clunky UI also doesn't help much.<p>As a python developer, I'm glad to see this and will surely give this a try shortly. Thanks!
I've been using siege for load testing. I'll give this a go at some point.<p>I don't use python as much as I'd like and this seems like a good work related use-case for me.