This release is a pre-release and may not be stable for production use.
Locust
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.
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:
- Send real time reporting data to TimescaleDB and visualize it in Grafana
- Wrap calls to handle the peculiarities of your REST API
- Use a totally custom load shape/profile
- ...
VS Code extension
Microsoft has built an excellent VS Code extension that uses Copilot to help you create and run Locust tests. Here's a video to get you started:
Azure Load Testing
Azure offers a managed load-testing service that lets you run and scale Locust tests easily.
- Scalable and flexible, with no need to host your own infrastructure
- If your application is hosted on Azure, it can combine test results with detailed resource metrics to help pinpoint bottlenecks and optimize performance.
- Integrates well with Azure DevOps and GitHub for CI/CD pipelines, enabling automated performance testing as part of your development workflow.
Links
- Documentation: docs.locust.io
- Support/Questions: StackOverflow
- Chat/discussion: Discord
- Blog: medium.com
Authors
- Maintainer: Lars Holmberg
- UI: Andrew Baldwin
- Original creator: Jonatan Heyman
- Massive thanks to all of our contributors
Special thanks
License
Open source licensed under the MIT license (see LICENSE file for details).
Release files for locust 2.46.8.dev47
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| locust-2.46.8.dev47.tar.gz | 1.5 MB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| locust-2.46.8.dev47-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 3.0 MB
Release files / locust-2.46.8.dev47.tar.gz
| Download URL | locust-2.46.8.dev47.tar.gz |
|---|---|
| Size | 1.5 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2b4968d2091735da3315191b0616c45b5ecb747f5b4183e27dce85e9dcbd9025
|
|
BLAKE2b-256 checksum How to use checksums |
b8f8813563c1128917373a6d77901176deee95ab93ccb3c2cbdc4c532d8196fd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Release files / locust-2.46.8.dev47-py3-none-any.whl
| Download URL | locust-2.46.8.dev47-py3-none-any.whl |
|---|---|
| Size | 1.5 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b8d484f7f8ee671c227edcf0583fff91b71c8b57fe5da7b91c79ae905f2287b3
|
|
BLAKE2b-256 checksum How to use checksums |
0a3777b4afd01bbdb0049c21b1074a6f70542d70d3243667b50b5c09de370806
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Security for locust 2.46.8.dev47
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
