<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>eatonphil</author><text>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.&lt;p&gt;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.&lt;p&gt;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&amp;#x27;t need something a whole lot simpler.</text><parent_chain></parent_chain></comment><story><title>Locust – A modern load testing framework</title><url>http://locust.io/</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>dalyons</author><text>Used it for some substantial loadtesting, loved it. 
It&amp;#x27;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.</text><parent_chain></parent_chain></comment><story><title>Locust – A modern load testing framework</title><url>http://locust.io/</url></story>