Proa
Emerging · Rust · engine: hyper · tuned configuration · completeness 4/4
Compiled Proa HTML components served over thread-per-core Axum/Hyper workers with mimalloc v2, sonic-rs JSON serialization, thread-local libdeflater gzip compression, TLS 1.3 (AES-128-GCM via aws-lc-rs) on :8081, and per-worker deadpool-postgres pools.
- Official repository
- Official website
- Benchmark implementation
- All Rust entries, compared
- Open the leaderboard
Achievements
🥇 6 Gold · 🥈 3 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 · Database | 1 of 5 |
| 🥇 Gold | Family composite | Composite · HTTP/1.1 | 1 of 110 |
| 🥇 Gold | Within its language | Rust · Database | 1 of 3 |
| 🥇 Gold | Within its language | Rust · HTTP/1.1 | 1 of 12 |
| 🥇 Gold | Test profile | Database · Fortunes | 1 of 5 |
| 🥇 Gold | Test profile | Workload · JSON Comp | 1 of 105 |
| 🥈 Silver | Test profile | Database · Async DB | 2 of 5 |
| 🥈 Silver | Test profile | Efficiency · Latency-1M | 2 of 110 |
| 🥈 Silver | Test profile | Workload · JSON TLS | 2 of 106 |
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.
Every result
Alpha Round, 12 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 | 3,114,432 | 1.31ms | 2.48ms | 6627.7% | 224MiB |
| Connection | Pipelined | 4,096 | 17,497,568 | 3.75ms | 6.54ms | 6258.2% | 207MiB |
| Connection | Short-lived | 4,096 | 2,464,129 | 1.64ms | 4.87ms | 6066.4% | 260MiB |
| Concurrency | Async Delay | 32,000 | 2,314,810 | 13.82ms | 17.00ms | 5029.1% | 749MiB |
| Efficiency | Latency-10K | 1,024 | 9,979 | 78.3us | 103.0us | 23.6% | 152MiB |
| Efficiency | Latency-1M | 1,024 | 998,517 | 96.7us | 181.0us | 2619.0% | 148MiB |
| Workload | JSON Comp | 4,096 | 812,119 | 5.05ms | 11.10ms | 6259.4% | 274MiB |
| Workload | JSON Comp | 16,384 | 779,949 | 20.99ms | 30.90ms | 6672.0% | 612MiB |
| Workload | JSON TLS | 4,096 | 1,580,024 | 2.55ms | 56.24ms | 6316.8% | 351MiB |
| Workload | 8Gbit | 512 | 49,084 | 92.9us | 118.0us | 204.8% | 178MiB |
| Database | Async DB | 1,024 | 354,354 | 2.89ms | 18.10ms | 3036.8% | 226MiB |
| Database | Fortunes | 1,024 | 222,969 | 4.59ms | 6.94ms | 3286.2% | 239MiB |
Compared with
The Rust web frameworks around Proa 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.
| Entry | Composite | vs Proa | |
|---|---|---|---|
| cpeak | 6920 | -7% | head to head |
| ntex | 6559 | -12% | head to head |
Compare Proa with any Rust entry · Compare Proa with any entry, in any language · Every Rust entry, ranked
Results updated · How the benchmark is run · The machine · Add or fix an entry