HttpArena
Frameworks

viltrum

Emerging · V · tuned configuration · completeness 4/4

HTTP framework for V with its own HTTP/1.1 engine: router with :params, middleware chain, first-party WebSocket, strict request framing (Content-Length and chunked, smuggling-hardened, fuzzed in CI). Tuned: one SO_REUSEPORT epoll loop per CPU (epoll_cores) instead of the default thread-per-connection I/O. json-comp uses viltrum's gzip middleware.

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.

FamilyRankComposite
HTTP/1.192 of 97405
WebSocket23 of 31515

Every result

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

CategoryProfileConnsReq/secAvgp99CPUMemory
ConnectionBaseline4,096585,5947.03ms17.70ms1871.9%124MiB
ConnectionPipelined4,096878,12874.40ms116.40ms1291.7%150MiB
ConnectionShort-lived4,096538,6757.58ms30.20ms2267.3%131MiB
WorkloadJSON Comp4,09614,418276.28ms454.20ms2249.2%177MiB
WorkloadJSON Comp16,38417,366847.75ms1.16s2398.3%481MiB
WebSocketEcho5122,371,734215us420us6100.6%106MiB
WebSocketEcho4,0962,132,0251.79ms3.46ms5729.9%462MiB
WebSocketEcho16,3841,691,0084.55ms17.60ms5718.8%1.0GiB

Compared with

The V entries around viltrum on the HTTP/1.1 composite, and the one leading them. The last column shows every profile side by side.

EntryCompositevs viltrum
vanilla-io_uring6224+1438%head to head
vanilla-epoll5531+1267%head to head

Compare viltrum with any V entry · Compare viltrum with any entry, in any language · Every V entry, ranked

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