HttpArena
Frameworks

axum

Flagship · Rust · engine: hyper · standard configuration

Axum 0.8 on hyper with the multi-threaded Tokio runtime, default configuration. Routing and path/query extractors through the Axum API, serde_json via the Json response, gzip through the tower-http compression layer.

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. The field is this entry's own league: engines and reverse proxies are scored apart from frameworks. How it works.

FamilyRankComposite
HTTP/1.161 of 71122

Every result

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

CategoryProfileConnsReq/secAvgp99CPUMemory
ConnectionBaseline512432,2721.11ms4.79ms2174.5%61MiB
ConnectionBaseline4,096755,8951.79ms11.30ms3178.0%124MiB
ConnectionPipelined5125,822,8161.30ms3.30ms6158.7%45MiB
ConnectionPipelined4,0966,500,1425.01ms16.70ms6549.7%106MiB
ConnectionShort-lived512312,369676us3.80ms1332.7%49MiB
ConnectionShort-lived4,096315,827854us3.83ms1313.4%53MiB
WorkloadJSON4,096216,2991.02ms15.00ms1525.8%43MiB
WorkloadJSON Comp512113,0071.88ms26.90ms4129.0%66MiB
WorkloadJSON Comp4,096107,4632.56ms28.60ms4391.3%60MiB
WorkloadJSON Comp16,384100,8372.74ms32.30ms2706.1%90MiB
WorkloadUpload321,40322.77ms78.20ms2948.3%1.5GiB
WorkloadUpload2561,487166.16ms937.40ms4974.6%4.9GiB

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