epoxide
Engine · C# · engine: epoll
epoxide — ioxide's thread-per-core runtime on epoll instead of io_uring, on its raw recv/send API and nothing above it: the edixoi entry on the other kernel interface. One reactor per core, each owning its epoll set and its share of the SO_REUSEPORT listeners. A recv or a send is an ordinary syscall on the handler's own thread; a read or flush that has to wait parks on the reactor, which finishes it at the next readiness edge and resumes the handler inline. The HTTP/1.1 handling (request line, query string, case-insensitive headers, Content-Length and chunked bodies, keep-alive, pipelining, reads fragmented across recv boundaries) is edixoi's, hand-written against that API — no framework, no router. One handler answers on both doors: plaintext on :8080, and TLS on :8081 for json-tls and the 8gbit echo, terminated on the BoringSSL ioxide bundles, with kernel TX offload and BoringSSL receive. The async profile's wait is a deadline in the reactor's own timer queue, so a held connection costs a timer rather than a thread. Companion to edixoi, which serves the same profiles on ioxide's io_uring ring.
Achievements
🥈 3 Silver · 🥉 1 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.
| Medal | Award | Field | Rank |
|---|---|---|---|
| 🥈 Silver | Family composite | Composite · HTTP/1.1 | 2 of 40 |
| 🥈 Silver | Within its language | C# · HTTP/1.1 | 2 of 8 |
| 🥈 Silver | Test profile | Connection · Short-lived | 2 of 40 |
| 🥉 Bronze | Test profile | Workload · JSON TLS | 3 of 27 |
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 | 2 of 40 | 6737 |
Every result
Alpha Round, 7 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 | 4,109,662 | 996us | 1.35ms | 6230.7% | 190MiB |
| Connection | Short-lived | 4,096 | 2,730,297 | 1.37ms | 2.26ms | 5739.8% | 885MiB |
| Concurrency | Async Delay | 32,000 | 2,714,278 | 11.68ms | 14.10ms | 5234.5% | 3.2GiB |
| Efficiency | Latency-10K | 1,024 | 9,981 | 71.4us | 103.0us | 22.0% | 79MiB |
| Efficiency | Latency-1M | 1,024 | 997,953 | 90.5us | 164.0us | 2170.3% | 92MiB |
| Workload | JSON TLS | 4,096 | 1,808,341 | 1.36ms | 35.94ms | 6039.1% | 371MiB |
| Workload | 8Gbit | 512 | 49,346 | 89.7us | 118.0us | 184.3% | 141MiB |
Compared with
The C# entries around epoxide on the HTTP/1.1 composite, and the one leading them. The last column shows every profile side by side.
| Entry | Composite | vs epoxide | |
|---|---|---|---|
| genhttp-ioxide | 7309 | +8% | head to head |
| edixoi | 6785 | +1% | head to head |
| ioxide-pipes | 6372 | -5% | head to head |
| simplew-tuned | 5835 | -13% | head to head |
Compare epoxide with any C# entry · Compare epoxide with any entry, in any language · Every C# entry, ranked
Results updated · How the benchmark is run · The machine · Add or fix an entry