Go to file
Lars Holmberg 33055e775a Help linter a bit with tests, avoid warnings about "Analysis of function ... is skipped because it is unannotated" 2025-03-09 17:33:21 +01:00
.github clean up gh action 2025-03-09 14:46:50 +01:00
.vscode Merge branch 'master' into report-name 2024-11-03 22:47:41 +01:00
benchmarks benchmark: CL arguments description 2024-06-30 22:24:49 +02:00
docs changelog 2025-03-08 20:19:29 +01:00
examples fix error in example 2025-01-31 09:36:16 +01:00
locust Help linter a bit with tests, avoid warnings about "Analysis of function ... is skipped because it is unannotated" 2025-03-09 17:33:21 +01:00
.coveragerc Remove concurrency from coverage 2019-10-01 15:04:36 -04:00
.dockerignore Switch to uv/hatch instead of Poetry (#3039) 2025-02-17 11:36:49 +01:00
.git-blame-ignore-revs Ignore ruff 0.3.0 formatting updates from gitblame 2024-02-29 22:04:54 +01:00
.gitattributes Added .gitattributes file that should give us consistent line endings 2013-12-02 22:17:57 +01:00
.gitignore Switch to uv/hatch instead of Poetry (#3039) 2025-02-17 11:36:49 +01:00
.pre-commit-config.yaml chore(deps): update ruff in pre-commit, apply fixes 2024-11-09 12:28:15 +01:00
.readthedocs.yaml Switch to uv/hatch instead of Poetry (#3039) 2025-02-17 11:36:49 +01:00
CHANGELOG.md Update changelog 2025-02-24 14:49:43 +01:00
Dockerfile Bump uv to 0.6.5, regenerate lock file. 2025-03-09 14:46:40 +01:00
Dockerfile.ci Do a first run inside Dockerfile to create .pyc files 2025-03-09 14:41:13 +01:00
LICENSE Update LICENSE, fix license year (#3019) 2025-01-01 20:02:34 +01:00
Makefile Switch to uv/hatch instead of Poetry (#3039) 2025-02-17 11:36:49 +01:00
README.md fix readme image ref links 2025-01-14 11:12:41 +08:00
SECURITY.md Revert "Update SECURITY.md" 2023-08-29 21:55:33 +02:00
Vagrantfile Also switching the Vagrant file to use xenial since precise is past it's EOL. 2017-10-01 14:08:31 -04:00
generate_changelog.py Reduce the changelog downloaded to make it faster (but we need to remember to not commit deletion of the old stuff) 2024-06-07 21:39:17 +02:00
hatch_build.py Switch to uv/hatch instead of Poetry (#3039) 2025-02-17 11:36:49 +01:00
package.json Add command to package.json 2024-08-19 15:07:44 -04:00
pyproject.toml Help linter a bit with tests, avoid warnings about "Analysis of function ... is skipped because it is unannotated" 2025-03-09 17:33:21 +01:00
uv.lock Bump uv to 0.6.5, regenerate lock file. 2025-03-09 14:46:40 +01:00

README.md

Locust

PyPI Downloads Build Status GitHub contributors Support Ukraine Badge

Locust is an open source performance/load testing tool for HTTP and other protocols. Its developer-friendly approach lets you define your tests in regular Python code.

Locust tests can be run from command line or using its web-based UI. Throughput, response times and errors can be viewed in real time and/or exported for later analysis.

You can import regular Python libraries into your tests, and with Locust's pluggable architecture it is infinitely expandable. Unlike when using most other tools, your test design will never be limited by a GUI or domain-specific language.

To get started right away, head over to the documentation.

Features

Write user test scenarios in plain old Python

If you want your users to loop, perform some conditional behaviour or do some calculations, you just use the regular programming constructs provided by Python. Locust runs every user inside its own greenlet (a lightweight process/coroutine). This enables you to write your tests like normal (blocking) Python code instead of having to use callbacks or some other mechanism. Because your scenarios are “just python” you can use your regular IDE, and version control your tests as regular code (as opposed to some other tools that use XML or binary formats)

from locust import HttpUser, task, between

class QuickstartUser(HttpUser):
    wait_time = between(1, 2)

    def on_start(self):
        self.client.post("/login", json={"username":"foo", "password":"bar"})

    @task
    def hello_world(self):
        self.client.get("/hello")
        self.client.get("/world")

    @task(3)
    def view_item(self):
        for item_id in range(10):
            self.client.get(f"/item?id={item_id}", name="/item")

Distributed & Scalable - supports hundreds of thousands of users

Locust makes it easy to run load tests distributed over multiple machines. It is event-based (using gevent), which makes it possible for a single process to handle many thousands concurrent users. While there may be other tools that are capable of doing more requests per second on a given hardware, the low overhead of each Locust user makes it very suitable for testing highly concurrent workloads.

Web-based UI

Locust has a user friendly web interface that shows the progress of your test in real-time. You can even change the load while the test is running. It can also be run without the UI, making it easy to use for CI/CD testing.

Locust UI charts Locust UI stats Locust UI workers Locust UI start test

Can test any system

Even though Locust primarily works with web sites/services, it can be used to test almost any system or protocol. Just write a client for what you want to test, or explore some created by the community.

Hackable

Locust's code base is intentionally kept small and doesn't solve everything out of the box. Instead, we try to make it easy to adapt to any situation you may come across, using regular Python code. There is nothing stopping you from:

Authors

License

Open source licensed under the MIT license (see LICENSE file for details).