rewrk is a Rust command-line benchmarker that favors realistic concurrent HTTP workloads over pipelined request bursts. It supports HTTP/1, HTTP/2, latency percentiles, and cross-platform execution.
About
rewrk is a Rust command-line benchmarker that favors realistic concurrent HTTP workloads over pipelined request bursts. It supports HTTP/1, HTTP/2, latency percentiles, and cross-platform execution.
Best for
Quick HTTP or protocol micro-benchmarks from a single machine
Teams that prefer open-source licensing and self-hosting options
Groups comfortable scripting in Rust
Not the best fit when
Full multi-protocol enterprise journeys and rich business-flow reporting
Teams unwilling to operate generators, results storage, and scaling
Architecture and concurrency
rewrk is typically driven as a CLI micro-benchmark with Rust. It favors single-host or simple distributed runs rather than enterprise controller grids.
rewrk 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: ChillFish8. Deployment model: self-hosted. Free; MIT License. Confirm details against the official site and a short proof-of-concept in your environment.
How does rewrk differ from Vegeta?
Compared with Vegeta, scripting centers on Rust rather than Go. rewrk lists protocols HTTP, HTTPS, HTTP/2; Vegeta lists HTTP, HTTPS. Status is unknown 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 rewrk use?
rewrk uses Rust for scripting or scenario definition. Runtime model: CLI-driven request generation with a lightweight concurrency model suited to single-host benchmarks. OS support: Windows, macOS, Linux. Protocols: HTTP, HTTPS, HTTP/2. 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 rewrk?
rewrk 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; MIT License.
What are known limitations of rewrk?
rewrk 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: unknown. Always validate against your target protocols and scale with a proof-of-concept.