ioxide
Engine · C# · engine: io_uring
ioxide — a shared-nothing io_uring runtime for .NET, consumed as its published NuGet packages (ioxide, ioxide.pg, ioxide.file, ioxide.http2, ioxide.ngtcp2, ioxide.nghttp3). One ring per reactor thread: multishot accept/recv into provided buffer rings, inline IValueTaskSource continuations, raw-syscall io_uring (no liburing). The HTTP/1.1 handler (request line, headers, Content-Length + chunked bodies, keep-alive, pipelining, fragmented reads) is hand-written on the raw recv/send API; TLS terminates ring-natively (kTLS transmit offload, OpenSSL receive) on :8081, h2 over TLS (pure-C# ioxide.http2) on :8443, and HTTP/3 over QUIC (ngtcp2 + nghttp3) on udp:8443; async-db rides ioxide.pg's ring-native pooled Postgres driver (SCRAM-SHA-256), static on h1 reads the file descriptor straight into the connection's write slab (ioxide.file hands out descriptors, not bytes), so header and body leave in one flush with no intermediate buffer; h2/h3 serve the same assets from memory.
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 | 1 of 34 | 381 |
| HTTP/2 | 4 of 6 | 172 |
| HTTP/3 | 2 of 3 | 127 |
Every result
Alpha Round, 29 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 | 4,071,966 | 125us | 243us | 6324.4% | 267MiB |
| Connection | Baseline | 4,096 | 4,108,420 | 997us | 1.43ms | 6401.5% | 337MiB |
| Connection | Pipelined | 512 | 53,313,475 | 153us | 365us | 6408.6% | 226MiB |
| Connection | Pipelined | 4,096 | 54,413,228 | 1.20ms | 1.69ms | 6434.9% | 338MiB |
| Connection | Short-lived | 512 | 2,481,833 | 191us | 769us | 5294.0% | 324MiB |
| Connection | Short-lived | 4,096 | 2,542,305 | 1.49ms | 4.69ms | 5375.2% | 494MiB |
| Workload | JSON | 4,096 | 1,710,801 | 1.72ms | 14.70ms | 5975.3% | 815MiB |
| Workload | JSON Comp | 512 | 943,786 | 506us | 2.44ms | 5915.9% | 538MiB |
| Workload | JSON Comp | 4,096 | 913,860 | 4.43ms | 21.60ms | 6335.2% | 1.3GiB |
| Workload | JSON Comp | 16,384 | 907,184 | 17.92ms | 71.10ms | 5983.2% | 4.9GiB |
| Workload | JSON TLS | 4,096 | 1,789,165 | 1.94ms | 69.63ms | 6399.1% | 1.1GiB |
| Workload | Upload | 32 | 2,414 | 13.22ms | 61.30ms | 1984.0% | 440MiB |
| Workload | Upload | 256 | 2,405 | 103.72ms | 464.80ms | 4904.1% | 567MiB |
| Workload | Static | 1,024 | 927,258 | 1.07ms | 11.91ms | 6547.0% | 340MiB |
| Workload | Static | 4,096 | 907,692 | 4.53ms | 83.93ms | 6284.4% | 677MiB |
| Workload | Static | 6,800 | 879,614 | 7.74ms | 77.37ms | 6226.4% | 903MiB |
| Workload | Static TLS | 1,024 | 1,129,365 | 820.40us | 23.34ms | 6327.0% | 480MiB |
| Workload | Static TLS | 4,096 | 778,964 | 5.20ms | 113.03ms | 6358.9% | 1002MiB |
| Workload | Static TLS | 6,800 | 677,575 | 10.00ms | 189.64ms | 6254.4% | 1.7GiB |
| Database | Async DB | 1,024 | 361,761 | 2.21ms | 16.70ms | 2988.9% | 405MiB |
| Database | CRUD | 4,096 | 832,280 | 4.55ms | 29.20ms | 3371.2% | 656MiB |
| Multi-endpoint | API-4 | 256 | 72,058 | 1.45ms | 9.40ms | 283.8% | 133MiB |
| Multi-endpoint | API-16 | 1,024 | 246,352 | 2.03ms | 17.40ms | 1178.1% | 311MiB |
| HTTP/2 | Baseline | 256 | 10,334,592 | 2.08ms | 12.66ms | 4283.1% | 438MiB |
| HTTP/2 | Baseline | 1,024 | 12,269,287 | 6.79ms | 94.65ms | 5043.5% | 698MiB |
| HTTP/2 | Static | 256 | 1,145,072 | 7.31ms | 50.05ms | 5824.3% | 683MiB |
| HTTP/2 | Static | 1,024 | 923,698 | 34.22ms | 155.97ms | 5692.8% | 1.5GiB |
| HTTP/3 | Baseline | 64 | 3,777,603 | 1.11ms | 2.32ms | 3366.4% | 261MiB |
| HTTP/3 | Static | 64 | 534,779 | 8.48ms | 17.11ms | 3347.6% | 808MiB |
How the benchmark is run · The machine · Add or fix an entry