Research shows that if your application introduces latency of even a few milliseconds, your business revenue can suffer immensely. At Tag1, we often have clients approach us with concerns about high traffic. Load testing and performance tuning often elicit groans from architects and developers more interested in building features, but it is a critical step in the process to ensuring your web application can operate at scale under heavy load. Though other load testing ecosystems exist, most notably Locust, these suffer from certain disadvantages that make them less appealing for those concerned about scalability.
Goose is a powerful new open-source load testing tool written in Rust by the Tag1 team. Inspired by Locust, it offers many of the same advantages but makes far more efficient use of the underlying hardware. On a single core, the current version of Goose is at least eleven times faster than Locust, and this high level of scalability increases as you introduce additional cores. And fortunately for open-source contributors, Goose is entirely free and open-source, with the roadmap and vision to become a formidable player among load testing tools.
In this episode of Tag1 Team Talks, Jeremy Andrews (Founding Partner at Tag1) and Fabian Franz (VP Software Engineering at Tag1) joined Michael Meyers (Managing Director at Tag1) and your host and moderator Preston So (Editor in Chief at Tag1 and author of Decoupled Drupal in Practice) for a high- and low-level examination of what makes Goose great for even the most finicky load testing scenarios. Learn how you can substitute Goose for Locust and access all of the benefits of the Rust programming language alongside unique features that make Goose a compelling option for anyone concerned about performance and scalability.
- Goose load testing software
- Goose documentation
- Goose Attack Blog Post
- Rust Language
- Locust load testing tool
For a transcript of this video, see Transcript: Introducing Goose, a highly scalable load testing framework written in Rust - Tag1 TeamTalk #016.