Part of #151.
Why. The most defensible comparisons for celeris's kernel-bypass event-loop claim are the servers that contest it directly. (Per the design decision, do these BEFORE the cross-language TechEmpower leaders in #163.)
Scope — new adapters implementing the 6-endpoint contract (servers/common/contract.go):
- gnet (Go) — the canonical Go event-loop server; closest architectural peer to celeris's epoll engine. Highest-value Go omission.
- zap / http.zig (Zig) — event-loop server, direct peer to the iouring/epoll engines.
- Rust hyper (raw) — the floor everyone builds on; TechEmpower-grade baseline (we already have actix/axum/ntex above it).
Per adapter: own module/build dir, ready addr= handshake, -bind/-engine flags, contract endpoints, registry entry in servers/servers.go, feature flags.
Depends on #164 for Zig toolchain (Rust already provisioned).
Acceptance. All three appear as columns in static + concurrency scenarios with fair, idiomatic implementations.
Refs: servers/servers.go, servers/common/contract.go, servers/start.go.
Part of #151.
Why. The most defensible comparisons for celeris's kernel-bypass event-loop claim are the servers that contest it directly. (Per the design decision, do these BEFORE the cross-language TechEmpower leaders in #163.)
Scope — new adapters implementing the 6-endpoint contract (
servers/common/contract.go):Per adapter: own module/build dir,
ready addr=handshake,-bind/-engineflags, contract endpoints, registry entry inservers/servers.go, feature flags.Depends on #164 for Zig toolchain (Rust already provisioned).
Acceptance. All three appear as columns in static + concurrency scenarios with fair, idiomatic implementations.
Refs:
servers/servers.go,servers/common/contract.go,servers/start.go.