node-h3
Flagship · JS · engine: nodehttp · standard configuration · completeness 4/4
H3 v2, the unjs framework under Nitro and Nuxt, served on node:http by srvx with the cluster module for multi-core scaling.
Achievements
🥈 2 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 |
|---|---|---|---|
| 🥈 Silver | Within its language | JS · HTTP/1.1 | 2 of 5 |
| 🥈 Silver | Test profile | Efficiency · Latency-10K | 2 of 71 |
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 | 26 of 71 | 2903 |
Every result
Alpha Round, 11 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 | 756,808 | 5.41ms | 7.31ms | 6488.0% | 2.5GiB |
| Connection | Pipelined | 4,096 | 1,637,607 | 39.96ms | 57.90ms | 6611.1% | 4.2GiB |
| Connection | Short-lived | 4,096 | 668,595 | 6.08ms | 96.90ms | 6431.8% | 5.8GiB |
| Concurrency | Async Delay | 32,000 | 922,461 | 34.41ms | 47.80ms | 6453.7% | 6.3GiB |
| Efficiency | Latency-10K | 1,024 | 9,983 | 134.2us | 238.0us | 113.1% | 2.2GiB |
| Efficiency | Latency-1M | 1,024 | 845,819 | 1243601.4us | 7251968.0us | 6484.1% | 2.5GiB |
| Efficiency | Latency-500K/8 | 1,024 | 137,826 | 7217273.4us | 14462976.0us | 769.5% | 585MiB |
| Workload | JSON Comp | 4,096 | 242,721 | 16.40ms | 376.30ms | 6377.2% | 7.3GiB |
| Workload | JSON Comp | 16,384 | 250,845 | 55.91ms | 1.47s | 6261.2% | 8.3GiB |
| Workload | JSON TLS | 4,096 | 507,727 | 7.99ms | 48.33ms | 6595.8% | 6.5GiB |
| Workload | 8Gbit | 512 | 49,366 | 268.5us | 702.0us | 1354.7% | 4.3GiB |
Compared with
The JS entries around node-h3 on the HTTP/1.1 composite, and the one leading them. The last column shows every profile side by side.
| Entry | Composite | vs node-h3 | |
|---|---|---|---|
| fulmine.js | 6248 | +115% | head to head |
| hyper-express | 4801 | +65% | head to head |
| ultimate-express | 4584 | +58% | head to head |
| fastify | 2444 | -16% | head to head |
| node | 2056 | -29% | head to head |
Compare node-h3 with any JS entry · Compare node-h3 with any entry, in any language · Every JS entry, ranked
Results updated · How the benchmark is run · The machine · Add or fix an entry