Locust’s cover photo
Locust

Locust

Technology, Information and Internet

San Francisco, California 358 followers

The most popular Python-based load/performance testing tool!

About us

Locust is known as one of the most flexible load testing tools, and it allows you to express test scenarios in regular Python code. It can be expanded with regular Python libraries or you can use contributions from the open source community. Locust Cloud / Locust Technologies Inc was shut down in 2026, but the open source project remains!

Website
https://github.com/locustio/locust/
Industry
Technology, Information and Internet
Company size
1 employee
Headquarters
San Francisco, California
Type
Nonprofit
Founded
2024

Locations

Employees at Locust

Updates

  • Locust reposted this

    🚀 Exciting news 🚀 Microsoft is now backing my work on Locust and bringing enterprise-grade scale load testing and seamless Azure integrations to the community! Check out the full article to see how you can now run your Locust scripts in the cloud using the Azure Portal or directly from VS Code using Microsoft's excellent #Copilot-powered Locust extension. #LoadTesting #Locust #Python https://lnkd.in/dkayhTt6

  • New year, new challenges: Locust Cloud is shutting down 😕 After nearly two years of building a premium load testing platform, the exciting ride that was Locust Technologies is over. Our customers ran over 6,000 tests on our platform, and we helped identify real performance issues in both production and test environments. But as with most startups, growth is ultimately what matters, and in the end we simply weren't able to attract enough frequent users. So the decision was made to wind down the company. I'm grateful for all the things we got to explore along the way. We learned just how complex it is to build a multi-tenant SaaS solution for load testing — and how hard it can be to get customers to see the value of it! I'd like to personally thank everyone who has contributed. Especially our awesome engineers, Andrew Baldwin and Amadeu Pereira, but also Stephen Norman and Richard Aberman! The good news is that Locust (the open source project) remains freely available, and I'm still committed to maintaining and improving it. And most of the things we made as a company have been contributed to the open source project, courtesy of Open Core Ventures. There's still a lot of work to be done in modernizing load testing, and in the words of an actor you may have heard of: I'll be back! // Lars

  • View organization page for Locust

    358 followers

    Load Testing Just Got Observable — Thanks to Locust Cloud Technologies + OpenTelemetry! Locust now ships with native OpenTelemetry instrumentation — meaning you can stream telemetry straight into any OTel-compatible observability platform. With Observable Load Tests, scalability issues finally have nowhere to hide. You get the full picture: metrics + end-to-end distributed traces. ✨ Performance engineering just got a whole lot easier. Instead of wrestling with manual correlation, you follow a natural observability flow: ➡️ Metrics reveal when performance degrades ➡️ Traces reveal where and why (code? infra? dependencies?) 🔍 What OTel + Locust Unlocks Start-to-finish load test clarity across distributed services. Full trace visibility from load generator → application → every span including connection time! Clean load-test isolation from background traffic. True end-to-end insight tying code behavior to infra metrics (CPU, memory, K8s, cloud resources). Observable load testing is poised to become the new standard in performance engineering — and it’s going to spread fast. 🔥 At Locust, our mission is to help engineers create methodical load tests and make analysis dramatically simpler. https://lnkd.in/eBFWzJ9u #performanceengineering #devperfops Locust Cloud #opentelemetry #loadtesting #performancetesting #devops #observability #RCA #APM

  • Locust reposted this

    View organization page for Locust

    358 followers

    Big News for Performance Engineering: Observable Load Testing Has Arrived! Locust now supports native OpenTelemetry instrumentation, allowing you to send telemetry directly to any OTel-compatible observability platform. With Observable Load Tests, you can quickly uncover scalability bottlenecks using both metrics and end-to-end distributed traces. ✨ Performance engineering just got a Whole. Lot. Easier. Traditional load testing required extensive, manual correlation. Now, you simply follow the natural observability workflow: ➡️ Metrics show when performance begins to degrade ➡️ Traces show where and why (code? infrastructure? dependencies?) What OTel + Locust Gives You: Start-to-finish clarity - pinpoint exactly when the test starts, ramps, and ends across distributed services Full trace visibility - from the load generator through every backend hop (including that elusive connection time!) Load test isolation - load-test traffic is clearly separated from background noise True end-to-end insight - correlate code behavior with infra metrics like CPU, memory, K8s, and cloud resources Observable load testing will be the new norm in performance engineering — this news will spread like wildfire. 🔥 At Locust, we aim to help engineers more easily create and execute methodical load testing - and simplify analysis! If you’ve ever struggled to understand why your system slows under load…👉 Observable load testing changes everything. Try the Locust Cloud Free Tier: https://lnkd.in/emdwd45U https://lnkd.in/eBFWzJ9u #LoadTesting #OpenTelemetry #Observability #LocustCloud #PerformanceEngineering #DevOps #SRE #DevPerfOps #ObservableLoadTesting

  • View organization page for Locust

    358 followers

    Big News for Performance Engineering: Observable Load Testing Has Arrived! Locust now supports native OpenTelemetry instrumentation, allowing you to send telemetry directly to any OTel-compatible observability platform. With Observable Load Tests, you can quickly uncover scalability bottlenecks using both metrics and end-to-end distributed traces. ✨ Performance engineering just got a Whole. Lot. Easier. Traditional load testing required extensive, manual correlation. Now, you simply follow the natural observability workflow: ➡️ Metrics show when performance begins to degrade ➡️ Traces show where and why (code? infrastructure? dependencies?) What OTel + Locust Gives You: Start-to-finish clarity - pinpoint exactly when the test starts, ramps, and ends across distributed services Full trace visibility - from the load generator through every backend hop (including that elusive connection time!) Load test isolation - load-test traffic is clearly separated from background noise True end-to-end insight - correlate code behavior with infra metrics like CPU, memory, K8s, and cloud resources Observable load testing will be the new norm in performance engineering — this news will spread like wildfire. 🔥 At Locust, we aim to help engineers more easily create and execute methodical load testing - and simplify analysis! If you’ve ever struggled to understand why your system slows under load…👉 Observable load testing changes everything. Try the Locust Cloud Free Tier: https://lnkd.in/emdwd45U https://lnkd.in/eBFWzJ9u #LoadTesting #OpenTelemetry #Observability #LocustCloud #PerformanceEngineering #DevOps #SRE #DevPerfOps #ObservableLoadTesting

  • View organization page for Locust

    358 followers

    Let’s talk about performance engineering and manual investigations… Where’s the bottleneck - in the code or in the infrastructure? Picture this: You designed a load test with a load script that executes several business transactions or APIs, all targeting the same microservice with no external dependencies. As the test ramps, one specific transaction slows down… and that single degradation throttles the throughput of every other transaction in the script. The rest of the business transactions maintain steady, healthy response times. But there’s a definite plateau in the load test TPS even as the number of virtual users continues to increase. A tell tale sign of a bottleneck. 👉 That indicates a code-level bottleneck. And traditionally, isolating the underlying root cause requires painstaking manual analysis. But here’s the good news… You don’t have to do manual investigations anymore. With observability, you can instantly visualize the slow transactions - and investigate the bottleneck using the traces. See the span under the trace with the longest bar? What code executed? Observable load tests are here. And they’re about to change everything. 🚀 This coming Monday, Locust Cloud is dropping a deep-dive blog about Observable Load Testing. Performance engineering is about to get a whole. lot. easier. Buckle up. #LoadTesting #Observability #LocustCloud #OpenTelemetry #PerformanceEngineering #DevOps #SRE #Tracing #APM #Python #Microservices

  • View organization page for Locust

    358 followers

    The Evolution of Locust Load Testing 🚀 Open source Locust empowers engineers to create quick, flexible load scripts in Python that simulate realistic user behaviors. But until now, running Locust locally meant manually setting up distributed workers for load generation — and losing valuable insights once the test ended. Enter Locust Cloud. We provide on-demand, scalable cloud infrastructure and persistent reporting (up to 180 days) — so your test data doesn’t disappear when the test stops. And with native OpenTelemetry instrumentation, Locust load scripts can now seamlessly integrate with your observability platform for deep performance analysis and end-to-end visibility. 💡 Stay tuned for our upcoming blog: “Native OpenTelemetry with Locust Cloud”

  • Performance Engineering Without Observability Is Dead. RIP. Load Testing Gives You Yes/No Answers — Observability Tells You Why. Practical Steps to Integrate Performance Engineering with Observability. Choose the observability and load-testing stack you need for development and production. #performanceengineering #loadtesting #performancetesting #observability #opentelemetry

Similar pages

Browse jobs