# wrk

> wrk is an open source, self-hosted micro-benchmark CLI from wg / community, scripted in C, Lua.

- Canonical: https://perf.jmeter.ai/tools/wrk/
- Review: https://perf.jmeter.ai/reviews/wrk/
- Official: https://github.com/wg/wrk
- Source: https://github.com/wg/wrk
- Vendor: wg / community
- Category: Micro-benchmark CLI
- License: Open Source — Free; Apache License 2.0.
- Deployment: Self-hosted
- Status: Active
- Scripting: C, Lua
- Protocols: HTTP, HTTPS
- OS support: macOS, Linux
- First released: 2012
- Latest release: 4.2.0 (1970-01-01)
- Last verified: 2026-08-11

## What it is
wrk is a multithreaded HTTP benchmarking tool with LuaJIT scripting for custom workloads. It emphasizes throughput and latency measurements for HTTP services.

## Choose it when
- Quick HTTP or protocol micro-benchmarks from a single machine
- Teams that prefer open-source licensing and self-hosting options
- Groups comfortable scripting in C, Lua

## Look elsewhere when
- Full multi-protocol enterprise journeys and rich business-flow reporting
- Teams unwilling to operate generators, results storage, and scaling

## Architecture
wrk is typically driven as a CLI micro-benchmark with C, Lua. It favors single-host or simple distributed runs rather than enterprise controller grids.

## Pricing
wrk is open-source software, licensed under the Apache License 2.0 (as indicated by the LICENSE file in the repository), and is available for free.

## Compare
- [LoadRunner Professional vs wrk](https://perf.jmeter.ai/vs/loadrunner-professional-vs-wrk/) — The practical split is the cost model: LoadRunner Professional is commercial, wrk is open source.
- [wrk alternatives](https://perf.jmeter.ai/alternatives/wrk/)

## FAQ
### Who is wrk for?
wrk is best for developers who need fast HTTP or protocol micro-benchmarks from a terminal. It is open source, so teams can self-host and extend it. Vendor: wg / community. Deployment model: self-hosted. Free; Apache License 2.0. Confirm details against the official site and a short proof-of-concept in your environment.

### How does wrk differ from Vegeta?
Compared with Vegeta, scripting centers on C, Lua rather than Go. wrk lists protocols HTTP, HTTPS; Vegeta lists HTTP, HTTPS. Status is active versus active. Use the Test Rig to compare full specs side by side before a proof-of-concept. Confirm details against the official site and a short proof-of-concept in your environment.

### What scripting language and concurrency model does wrk use?
wrk uses C, Lua for scripting or scenario definition. Runtime model: CLI-driven request generation with a lightweight concurrency model suited to single-host benchmarks. OS support: macOS, Linux. Protocols: HTTP, HTTPS. Match these to how your team already authors tests and which systems you must drive under load.

### What is the cloud or enterprise path for wrk?
wrk is primarily self-hosted; teams typically run generators on their own machines, CI runners, or private cloud. Plan for generator capacity, network access to targets, and result storage yourself. As open source, commercial support or hosted siblings may exist separately. Check the official site. Pricing note: Free; Apache License 2.0.

### What are known limitations of wrk?
wrk limitations to weigh: CLI micro-benchmarks excel at raw HTTP throughput but usually lack enterprise scenario orchestration, rich reporting, and multi-protocol suites; self-hosted tools require you to provision, scale, and observe load generators yourself. Status: active. Always validate against your target protocols and scale with a proof-of-concept.

---
Curated by NaveenKumar Namachivayam (QAInsights) · methodology: https://perf.jmeter.ai/about/#methodology · corrections: https://github.com/QAInsights/Performance-Testing-Tools/issues/new?title=Tool%20submission%3A%20&body=Tool%20name%3A%20%0AOfficial%20URL%3A%20%0AWhat%20should%20be%20added%20or%20corrected%3F%20%0A