orisha

Engine · Koru

Koru HTTP server compiled to native code via Zig. 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	27 of 39	1523

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	501,761	8.17ms	12.30ms	6470.1%	206MiB
Connection	Pipelined	4,096	7,953,337	8.25ms	12.40ms	6212.4%	215MiB
Connection	Short-lived	4,096	361,621	11.32ms	23.40ms	5696.9%	214MiB
Efficiency	Latency-10K	1,024	9,982	68.1us	88.0us	17.9%	150MiB
Efficiency	Latency-1M	1,024	499,192	5000065.6us	9883648.0us	6387.5%	155MiB
Workload	JSON Comp	4,096	417,915	9.80ms	19.50ms	6005.6%	226MiB
Workload	JSON Comp	16,384	380,531	42.81ms	64.30ms	6164.8%	461MiB
Workload	JSON TLS	4,096	440,016	9.01ms	36.26ms	6224.1%	342MiB

Compared with

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

Entry	Composite	vs orisha
orisha-uring	4595	+202%	head to head

Compare orisha with any Koru entry · Compare orisha 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