3 ms·

Does anyone know how it compares to Gatling (http://gatling.io http://gatling.io) ?

• therealmarv 11y ago
  Gatling is far more advanced but both tools share similar architectural designs regarding how they handle lots of traffic. Locust is more leightweight (and I would say also more easy, but depends on your needs) and is missing good graphical presentations of results and you will not get a browser recorder with it.
• rdsubhas 11y ago
  I used Locust for a good long time around a year back, and here are some observations. Locust is awesome to start with, and has master/slave for spawning multiple servers, great for testing real concurrency with large loads. Gatling doesn't have master/slave mode yet. Main problems with Locust are: * Lack of good presentation of results (compare Gatling and Locust results, and Locust is very primitive) * Lack of Pipelines/Scenarios. This IMO was a big deal breaker for me. You can't say: "100% users hit the home screen, out of which 70% add a product, out of which 25% actually pay" etc. This is easily modeled with Gatling, and the same request session with same data falls through each scenario. I'm still following https://github.com/locustio/locust/issues/171 https://github.com/locustio/locust/issues/171 though, but I don't think they have any idea of implementing it.