HttpArena
Frameworks

apex-tuned

Engine · C · engine: apex

Apex HTTP engine in C23: shared-nothing thread-per-core epoll runtime, CPU affinity pinning, zero-copy buffer recycling, streaming HTTP parser with TCP fragmentation resilience, route parameter trie, middleware pipeline, Brotli compression, and tuned TLS 1.3.

Achievements

🥇 5 Gold · 🥈 1 Silver · 🥉 2 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.

MedalAwardFieldRank
🥇 GoldFamily compositeComposite · HTTP/21 of 17
🥇 GoldWithin its languageC · HTTP/1.11 of 3
🥇 GoldTest profileConnection · Short-lived1 of 46
🥇 GoldTest profileHTTP/2 · Baseline1 of 16
🥇 GoldTest profileHTTP/2 · Baseline (h2c)1 of 14
🥈 SilverTest profileEfficiency · Latency-10K2 of 44
🥉 BronzeTest profileConnection · Baseline3 of 46
🥉 BronzeTest profileHTTP/2 · Static3 of 16

Composite rank

Each profile of a family is worth 1,000 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.

FamilyRankComposite
HTTP/1.15 of 466420
HTTP/21 of 172855

Every result

Alpha Round, 21 runs. Requests per second is the best of three; latency, CPU and memory come from that run.

CategoryProfileConnsReq/secAvgp99CPUMemory
ConnectionBaseline4,0964,403,856929us1.96ms6194.6%250MiB
ConnectionPipelined4,09659,539,9611.10ms1.39ms6036.2%241MiB
ConnectionShort-lived4,0962,822,8031.32ms1.80ms5870.1%255MiB
ConcurrencyAsync Delay32,0001,997,03615.88ms21.50ms2896.4%370MiB
EfficiencyLatency-10K1,0249,98373.4us110.0us26.7%219MiB
EfficiencyLatency-1M1,024998,04279.4us138.0us2077.8%224MiB
EfficiencyLatency-500K/81,024498,5237021.5us88160.0us775.1%48MiB
WorkloadJSON Comp4,096889,8084.58ms13.40ms6715.3%246MiB
WorkloadJSON Comp16,384865,00518.75ms46.00ms6738.4%341MiB
WorkloadJSON TLS4,0961,822,3831.39ms79.25ms5426.2%330MiB
Workload8Gbit51249,32590.2us116.0us226.4%241MiB
WorkloadStatic TLS1,0241,048,5751.00ms39.69ms6491.2%265MiB
HTTP/2Baseline25616,094,035839us30.55ms3076.9%244MiB
HTTP/2Baseline1,02416,030,2773.06ms86.69ms3217.3%310MiB
HTTP/2Static2561,431,6895.43ms189.12ms6466.6%268MiB
HTTP/2Static1,0241,424,82821.05ms213.27ms6529.9%343MiB
HTTP/2Baseline (h2c)25616,350,9161.03ms44.38ms1961.4%226MiB
HTTP/2Baseline (h2c)1,02416,634,9302.98ms16.26ms2912.8%287MiB
HTTP/2Baseline (h2c)4,09615,055,38312.93ms29.38ms2878.2%531MiB
HTTP/2JSON (h2c)1,0245,961,8553.57ms60.23ms4172.8%336MiB
HTTP/2JSON (h2c)4,0965,232,88421.16ms86.51ms6240.7%601MiB

Compared with

The C HTTP engines around apex-tuned on the HTTP/1.1 composite, and the one leading them. Entries of other leagues are left out: a composite does not carry from one league to another. The last column shows every profile side by side.

EntryCompositevs apex-tuned
mongoose5800-10%head to head
libreactorng3734-42%head to head

Compare apex-tuned with any C entry · Compare apex-tuned with any entry, in any language · Every C entry, ranked

Results updated · How the benchmark is run · The machine · Add or fix an entry