Documentation
Driller is a command-line HTTP load tester. Start with Getting started to install it and run a first test, then keep Benchmark syntax and the CLI reference at hand while writing plans.
Plans written for the original drill run unchanged;
Migrating from drill has the details.
Pages
-
Getting started
Install driller from crates.io or a release binary, run an ad-hoc test, then write a first benchmark plan.
-
Benchmark syntax
Every property of a benchmark plan: requests, assignments, includes, item and CSV loops, tags, and the interpolation variables.
-
Examples
Runnable benchmark plans and the axum fixture server that ships with the repository, and how to run each of them.
-
CLI reference
Every driller flag, the per-request and statistics output in text and JSON, and the tokio runtime tuning guide.
-
Proxies
Route load through HTTP and HTTPS proxies with the standard environment variables, and keep internal targets direct with NO_PROXY.
-
Migrating from drill
How driller relates to fcsonline/drill, what stays the same, and how to switch.
-
Contributing
How to propose a change, the quality checks every pull request must pass, and how releases are cut.