zix

Engine · Zig · engine: zix.Http1 URING Dispatch Model

HTTP/1.1 on the zix.Http1 raw engine, .URING dispatch: per-worker SO_REUSEPORT io_uring loops, comptime Router, staged send sink. Dual listener: cleartext 8080, TLS 1.3 on 8081. Database routes run on engine-worker lanes, each worker pumping its own pipelined postgrez connections on its ring with named prepared statements. No response cache and no startup pre-serialization anywhere: json serializes every field per request and compresses per request, static opens the file per request. The crud row cache is the 200 ms cache-aside the crud profile itself defines.

• Official repository
• Benchmark implementation
• All Zig entries, compared
• Open the leaderboard

Achievements

🥇 11 Gold · 🥈 2 Silver · 🥉 2 Bronze. Top three of a field, taken in this entry's own league: the family composite, the same composite among entries written in the same language, and each test profile it is scored on. Every field is the one the badges publish, so a medal and a badge always say the same thing. How medals are awarded.

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.

Every result

Alpha Round, 33 runs. Requests per second is the best of three; latency, CPU and memory come from that run.

Compared with

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

Compare zix with any Zig entry · Compare zix with any entry, in any language · Every Zig entry, ranked

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