Measurements with context

A basic same-host loopback comparison with Zap, measured on 6 September 2026. These results describe the initial Baz prototype c152e59, before package extraction.

Median requests per second at 32 connections / 2 client threads. Bar lengths share a zero baseline. Compare implementations within each host.

Host	Conn. / threads	Baz req/s	Zap req/s	Baz / Zap
macOS · M3 Max	32 / 2	254,261	245,054	1.038×
Linux · Core Ultra 7	32 / 2	363,594	205,310	1.771×
macOS · M3 Max	1 / 1	33,199	52,809	0.629×
Linux · Core Ultra 7	1 / 1	74,386	72,575	1.025×

macOS: Apple M3 Max. Linux: Intel Core Ultra 7 258V. Three paired trials per profile; one-second warmup and three-second measurements. ReleaseSafe with Zig assertions enabled, one server thread, 128 connection slots, a 13-byte response, keep-alive, no pipelining, and no CPU affinity.

The Mac’s one-connection result is lower than Zap’s. These short trials establish neither production capacity nor latency guarantees, and do not isolate Baz’s API overhead. The hosts used different wrk revisions; Zap retained its inherited C optimization and sanitizer settings.

All 24 measured trials completed with zero wrk-reported socket or non-2xx/3xx errors. Exact responses were checked before and after timing, rather than for every timed response. The report preserves ranges, versions, commands, raw results, and cleanup evidence.

Read the experiment and raw evidence