orisha-uring

Engine · Koru · engine: io_uring

Koru HTTP server compiled to native code via Zig — io_uring pump variant (per-worker ring + SO_REUSEPORT, multishot recv, kTLS). HttpArena routes wired through Orisha's handler seam. No response cache and no startup pre-serialization: json serializes every field per request and compresses per request.

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, less 2.5% for each of routing, middleware, request and response the entry does not do for you - its completeness factor, which the WebSocket and gRPC families do not carry. 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	11 of 39	4595

Every result

Alpha Round, 8 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	4,096	4,114,610	996us	1.39ms	6300.7%	445MiB
Connection	Pipelined	4,096	40,513,032	1.62ms	2.26ms	6363.7%	439MiB
Connection	Short-lived	4,096	2,665,265	1.42ms	3.05ms	5230.5%	527MiB
Efficiency	Latency-10K	1,024	9,979	71.0us	103.0us	22.1%	391MiB
Efficiency	Latency-1M	1,024	998,091	98.1us	163.0us	2080.6%	393MiB
Workload	JSON Comp	4,096	1,621,485	2.40ms	5.48ms	6613.6%	528MiB
Workload	JSON Comp	16,384	1,564,485	10.25ms	17.70ms	6634.7%	970MiB
Workload	JSON TLS	4,096	1,482,980	2.80ms	86.28ms	6304.6%	416MiB

Compared with

The Koru entries around orisha-uring on the HTTP/1.1 composite, and the one leading them. The last column shows every profile side by side.

Entry	Composite	vs orisha-uring
orisha	1523	-67%	head to head

Compare orisha-uring with any Koru entry · Compare orisha-uring with any entry, in any language · Every Koru entry, ranked

Results updated 2026-10-13 · How the benchmark is run · The machine · Add or fix an entry