Fiber v2 vs v3 benchmarks
In-process request benchmarks. Both versions run interleaved on the same CI machine, each with its own API and dependencies.
Overview
Requests per second on one CPU core, measured in-process without network, HTTP parsing or response writing. Higher is better.
Change in time per request
Details
Reading the numbers
- Requests per second are one divided by the median time per request on a single CPU core. A real server adds network, HTTP parsing and response writing, so production throughput is lower.
- Each round runs v2 and v3 of a scenario back to back, alternating which goes first. A time change is the median of these paired v3/v2 ratios, so load on the CI host that hits both halves of a pair cancels out. It can differ slightly from the ratio of the two medians.
- Thin gray bars and ~ mean no significant difference: the sign-test interval of a time change includes zero, or benchstat found p ≥ 0.05 for memory, allocations and snapshots from before paired rounds. A run whose median interval is ±5% or wider gets twice the rounds.
- Compare versions within one snapshot. CI machines differ between snapshots, so absolute numbers do not carry over.
fasthttp_floorruns no Fiber code and shows what the fasthttp upgrade alone changes.