tokio-uring
Engine · Rust · engine: io_uring
Minimal HTTP/1.1 server on tokio-uring — the io_uring-backed Rust runtime with a completion/owned-buffer API. A hand-rolled request parser (Content-Length + chunked bodies, keep-alive, pipelining, fragmented reads), one runtime per core with SO_REUSEPORT. No HTTP framework.
Composite rank
Each profile of a family is worth 100 to the entry that leads it, and the composite is the sum over the family. The field is this entry's own league: engines and reverse proxies are scored apart from frameworks. How it works.
| Family | Rank | Composite |
|---|---|---|
| HTTP/1.1 | 15 of 34 | 168 |
Every result
Alpha Round, 6 runs. Requests per second is the best of three; latency, CPU and memory come from that run.
| Category | Profile | Conns | Req/sec | Avg | p99 | CPU | Memory |
|---|---|---|---|---|---|---|---|
| Connection | Baseline | 512 | 3,380,500 | 150us | 315us | 6512.2% | 45MiB |
| Connection | Baseline | 4,096 | 3,565,878 | 1.15ms | 1.72ms | 6627.1% | 175MiB |
| Connection | Pipelined | 512 | 46,383,110 | 175us | 369us | 6496.7% | 44MiB |
| Connection | Pipelined | 4,096 | 48,876,057 | 1.34ms | 2.11ms | 6577.5% | 177MiB |
| Connection | Short-lived | 512 | 2,219,613 | 217us | 752us | 5728.2% | 94MiB |
| Connection | Short-lived | 4,096 | 2,636,459 | 1.51ms | 20.50ms | 6395.8% | 187MiB |
How the benchmark is run · The machine · Add or fix an entry