edixoi
Engine · C# · engine: io_uring
edixoi — the ioxide io_uring runtime on the raw recv/send API, and nothing above it. One reactor per core, each owning its ring and its share of the SO_REUSEPORT listeners; multishot accept and recv into provided buffer rings, with continuations resuming inline on the reactor thread that took the request. 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 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 ring-natively with kernel TX offload where the kernel offers the ULP (OpenSSL otherwise) and OpenSSL receive. The async profile's wait is an IORING_OP_TIMEOUT through ioxide.timer, so a held connection costs a kernel deadline rather than a thread. Companion to the ioxide-pipes entry, which serves the same profiles over System.IO.Pipelines.
Achievements
🥇 5 Gold · 🥈 1 Silver. 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 |
|---|---|---|---|
| 🥇 Gold | Family composite | Composite · HTTP/1.1 | 1 of 39 |
| 🥇 Gold | Within its language | C# · HTTP/1.1 | 1 of 7 |
| 🥇 Gold | Test profile | Concurrency · Async Delay | 1 of 18 |
| 🥇 Gold | Test profile | Connection · Short-lived | 1 of 39 |
| 🥇 Gold | Test profile | Workload · 8Gbit | 1 of 19 |
| 🥈 Silver | Test profile | Workload · JSON TLS | 2 of 26 |
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 | 1 of 39 | 6785 |
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,138,130 | 987us | 1.37ms | 6434.5% | 1.3GiB |
| Connection | Short-lived | 4,096 | 2,738,922 | 1.36ms | 2.19ms | 5566.2% | 2.3GiB |
| Concurrency | Async Delay | 32,000 | 2,833,966 | 11.23ms | 12.70ms | 6278.6% | 5.0GiB |
| Efficiency | Latency-10K | 1,024 | 9,979 | 69.6us | 99.0us | 22.4% | 1.2GiB |
| Efficiency | Latency-1M | 1,024 | 997,602 | 94.4us | 168.0us | 2235.6% | 1.2GiB |
| Workload | JSON TLS | 4,096 | 1,839,185 | 1.38ms | 36.34ms | 5795.8% | 1.5GiB |
| Workload | 8Gbit | 512 | 49,394 | 90.4us | 116.0us | 184.8% | 3.2GiB |
Compared with
The C# entries around edixoi on the HTTP/1.1 composite, and the one leading them. The last column shows every profile side by side.
| Entry | Composite | vs edixoi | |
|---|---|---|---|
| genhttp-ioxide | 7309 | +8% | head to head |
| ioxide-pipes | 6372 | -6% | head to head |
| simplew-tuned | 5834 | -14% | head to head |
Compare edixoi with any C# entry · Compare edixoi with any entry, in any language · Every C# entry, ranked
Results updated · How the benchmark is run · The machine · Add or fix an entry