← Directory

locust

Web server stress test locustfile.py is required in /mnt/locust/ See here for examples: https://docs.locust.io/en/stable/writing-a-locustfile.html

  • Development
  • Tools & Utilities
Web server stress test locustfile.py is required in /mnt/locust/ See here for examples: https://docs.locust.io/en/stable/writing-a-locustfile.html

Platform availability

Available on 3 of 9 platforms

  • Unraid
  • TrueNAS
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

81/100 Excellent

Maintained
100last commit 8 days ago
Popular
8928,202 GitHub stars
Easy to install
452 install platforms, install notes, Docker image
Light to run
No data
Security check
67no serious findings, 8 minor, CI, tests, OpenSSF Scorecard 6.3/10

Based on 4 of 5 factors.

Availability: platform listings confirmed today, links checked 15 days ago

GitHub stars
28,202
Open issues
4
Last commit
2026-10-04
Latest release
2.46.7
License
MIT
Activity
steady

Checked 6 days ago - source: GitHub (locustio/locust)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is supported.

Checked 15 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Check Locust runs with uvx Use the command 'uvx locust -V' to verify the basic install; uvx is a one-off Python runner that creates a throwaway environment, so you do not need to manage a permanent Python setup. If the version number appears, you are ready to point Locust at a target and start a test. source
  • Set target URL and UI port 8089 The host setting is the website or API that Locust's simulated users will visit, and the web UI listens on network port 8089 in the example. Set the target correctly and open port 8089 on remote machines, otherwise the users may fail to connect or your browser won't find the dashboard. source
  • Start Docker workers if needed If you run Locust with Docker Compose, use 'docker-compose up' to start it, and add --scale worker=4 when you need more simulated users. Workers are the containers that actually generate traffic, so too few workers can limit how much load you can run. source

Fetched 14 days ago - each note links to its source

Alternatives (2)

  • Apache JMeter - Apache JMeter is an open source Java application, designed to load test functional behavior and measure performance.
  • OctoPerf

Checked 12 days ago - source: AlternativeTo

Common questions

How do I point Locust at the system under test and make the dashboard reachable?

Set the host setting to the website or API that Locust's simulated users will visit, and open port 8089 on remote machines for the web UI. If the target or port is wrong, the users may fail to connect or the browser will not find the dashboard.

How can I run more simulated users with Docker Compose?

Start the stack with docker-compose up, and add --scale worker=4 when you need more simulated users. Workers are the containers that actually generate traffic, so too few workers can limit how much load you can run.

How can I verify a Locust installation when using uvx?

Run uvx locust -V to verify the basic install. uvx is a one-off Python runner that creates a throwaway environment, so you do not need to manage a permanent Python setup. If the version number appears, you are ready to point Locust at a target and start a test.

What should I check first when a load test returns 5xx, connection aborted, or connection reset errors?

Check your server logs. If it works at low load, it is almost certainly not a Locust issue, but an issue with the system you are testing.

How do I make each task iteration look like a new user to the system under test?

Call self.client.cookies.clear() at the end of your task. This clears cookies so the next task iteration seems like a new user to the system under test.

Answers sourced from docs.locust.io, github.com, github.com, github.com

Community

Collected 14 days ago - public community threads