swerverts
Experimental · TS · engine: swerver · standard configuration · completeness 4/4
TypeScript route handlers running in-process on the swerver (Zig) engine via an FFI park/resume bridge: a matched request is handed from the reactor to a Bun handler and its response taken back, with no socket hop. The engine installs as a platform prebuilt (no build step) and fans out one worker per core over SO_REUSEPORT. HTTP/1.1 only for now; the prebuilt is built without the native-only TLS/HTTP2/HTTP3 flags.
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 | 7 of 7 | 779 |
Every result
Alpha Round, 3 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 | 1,280,248 | 3.20ms | 9.92ms | 6407.7% | 3.3GiB |
| Connection | Pipelined | 4,096 | 1,442,572 | 44.99ms | 83.80ms | 6581.3% | 3.3GiB |
| Connection | Short-lived | 4,096 | 1,147,351 | 3.56ms | 12.20ms | 6250.3% | 3.0GiB |
Compared with
The TS entries around swerverts on the HTTP/1.1 composite, and the one leading them. The last column shows every profile side by side.
| Entry | Composite | vs swerverts | |
|---|---|---|---|
| bun | 5852 | +651% | head to head |
| deno | 2011 | +158% | head to head |
| hono-node | 1811 | +132% | head to head |
Compare swerverts with any TS entry · Compare swerverts with any entry, in any language · Every TS entry, ranked
Results updated · How the benchmark is run · The machine · Add or fix an entry