Benchmarks
Wisp's first rule is zero cost on the request hot path. This page is what is measured and how to run it. The measured numbers, losses included, are on the home page and in bench/tfb/RESULTS.md.
git clone https://github.com/wyziedevs/wisp
cd wisp
cargo run -r -p bench-run -- --paths fortunes
You need Rust. bench/README.md lists every option, the frameworks compared, and how each path is checked for identical output before it is measured. Results depend on the machine: read them as a comparison on one machine, not as absolutes.
What Is Checked
| Check | What it does |
|---|---|
| Instructions per request | A change that touches the request path runs A/B against the build before it, counting CPU instructions for the same requests. A feature a route does not use must add none. |
| Startup self-tests | Each fast path (the I/O driver, parsers, caches) is proven at server start, and falls back to the plain path if the proof fails. |
| Comparable frameworks | bench/ holds the same server-rendered page, JSON and plaintext routes written the way each framework's docs would write them, a load generator and a runner. |
Tokens
Writing cost is measured by a program in the repository: cargo run -p wisp-tokens --release. See Tokens.
Is This Page Useful?