Install vegeta with Homebrew, MacPorts, Nix, pacman, scoop, zypper

Project links

• Homepage
• Upstream docs
• Package manager page

Commands and aliases

• vegeta

Project history

The public project dates to 2013, with secondary software cataloging and the upstream repository tying the first release era to August 2013. The repository's README frames the tool as something built from the need to drill HTTP services at a constant request rate, and the project has remained a compact Go utility rather than growing into a hosted load-testing service.

Over time Vegeta settled into the Unix-pipeline shape that package users recognize: `vegeta attack` generates binary result streams, `vegeta report` summarizes them, `vegeta plot` creates an HTML visualization, and the library package lets Go programs embed the attacker directly.

Adoption history

Vegeta became popular with operators and backend developers who wanted a small, scriptable load generator that could be installed from language, OS, and package-manager channels. Tutorials from cloud providers and performance-testing blogs continue to teach it as a practical way to validate request-per-second targets and latency behavior for HTTP APIs.

Its adoption has been strongest in the space between heavyweight test suites and commercial load-testing platforms: teams use it for quick pre-production checks, regression comparisons, and reproducible command-line benchmarks.

How it is used

Typical use is a pipeline such as emitting target lines, running `vegeta attack` with a rate and duration, then piping the encoded results to `vegeta report` or saving them for later plotting. More advanced users provide target files with methods, headers, and bodies, or use the Go library to generate traffic from test harnesses.

Because Vegeta tries to sustain a specified rate, package users pay attention to concurrency and overload behavior: if the system under test slows down, the attacker may need more workers to keep the rate, which is useful for stress testing but can intensify an already overloaded target.

Why package nerds care

In package-manager terms, Vegeta is the sort of tool people install because it composes cleanly with shells, CI jobs, and simple HTTP fixtures. It is small, portable, and memorable enough that the binary name itself has become shorthand for a constant-RPS smoke test.

Timeline

• 2013: Vegeta appears publicly as an HTTP load-testing tool written in Go.
• 2015: GitHub issue discussions show users pushing on overload detection and concurrency behavior, reflecting real operational use.
• 2020s: Cloud-provider and community tutorials continue to present Vegeta as a lightweight CLI for API and service load testing.

Related projects

• Vegeta is often considered alongside ApacheBench, wrk, k6, JMeter, Locust, Gatling, and GoReplay. Its closest niche is the small reproducible CLI benchmark, especially when a constant request rate matters more than browser-like scenario scripting.

Sources

• https://en.wikipedia.org/wiki/Vegeta_(software)
• https://github.com/tsenart/vegeta
• https://github.com/tsenart/vegeta/issues/126
• https://pkg.go.dev/gopkg.in/tsenart/vegeta.v10
• https://www.scaleway.com/en/docs/tutorials/load-testing-vegeta/