Skip to content

Series of experiments with load testing tool called Locust (locust.io)

Notifications You must be signed in to change notification settings

aporquez/locust-experiments

 
 

Repository files navigation

Recently we were supposed to conduct a load/stress testing session.

There were already some python scripts in place and the team that produced them suggested using locust.io for this purpose.

The tool was new to me. At the first glance, as far as the feature list is concerned, Locust seems inferior to other software we used before, like Gatling or even JMeter (the latter is turning 20 soon, but it doesn't make it an invalid testing tool!). It looks like Locust generates load and that's pretty much it. With the exception of the single feature that I think is its strongest selling point: the ability to distribute the load (single master, multiple slaves) out of the box.

The authors also claim that it's very easy to use and to extend Locust. So, instead of discarding it (using Locust), I decided to give it a quick try and try to address potential needs/problems with a series of quick experiments.

Some of the things I would like to confirm are:

This repo holds results of particular experiments.

Much of the staff included here is described here: https://medium.com/locust-io-experiments.

About

Series of experiments with load testing tool called Locust (locust.io)

Resources

Stars

Watchers

Forks

Packages

No packages published

Languages

  • Python 75.2%
  • Dockerfile 9.8%
  • Shell 8.8%
  • HTML 6.2%