locustio/locust

Write scalable load tests in plain Python πŸš—πŸ’¨

View on GitHub β†—Jump to charts ↓Open shareable report β†’

Summary Information

Updated 33 minutes ago
Added to GitGenius on September 2nd, 2026
Created on February 17th, 2011
Open Issues & Pull Requests: 4 (+0)
GitHub issues: Enabled
Number of forks: 3,242
Total Stargazers: 28,133 (+0)
Total Subscribers: 419 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 4.3 hours
Mean response time: 7.6 days
90th percentile: 24.2 days
Tracked items: 164

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Only 9% of issues opened in the past year have been closed. Three people close 76% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 3
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 62 days
Stale 30+ days: 1
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (93)
  • stale (64)
  • feature request (58)
  • invalid (15)
  • hacktoberfest (4)
  • non-critical (3)
  • duplicate (2)
  • cantfix (1)

Detailed Description

Locust is a load testing tool that lets you write performance tests in plain Python code.

Locust addresses the problem of defining load tests without being constrained by graphical interfaces or domain-specific languages. It works by letting developers write test scenarios as regular Python code, with each simulated user running inside its own greenletβ€”a lightweight coroutine that allows blocking code to execute concurrently. This approach means you can use standard Python control flow, import libraries, and leverage your normal development environment and version control systems instead of working with XML, binary formats, or GUI-based test builders.

Locust suits teams that want to version control their tests as code and avoid vendor lock-in to proprietary test definition formats. It works well for testing HTTP and other protocols at scale, supporting hundreds of thousands of concurrent users across distributed machines. The tool offers both a web-based UI for real-time monitoring and command-line operation for CI/CD integration, with the ability to adjust load during a running test. The event-based architecture using gevent keeps per-user overhead low, making it particularly effective for highly concurrent workloads where you need many simultaneous connections on modest hardware.

The project maintains steady activity with regular commits addressing bug fixes, feature additions, and documentation improvements. Development includes ongoing work to expand protocol support beyond HTTP and to enhance the distributed testing capabilities. The maintainers actively respond to issues and pull requests, indicating sustained engagement with the user base. The codebase receives updates that refine the core greenlet-based execution model and improve the web UI's real-time reporting features.