hono-bun
Flagship · TS · engine: jsc · standard configuration · completeness 4/4
Ultrafast Web Standards framework running natively on Bun — no adapter overhead.
Achievements
🥉 1 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.
| Medal | Award | Field | Rank |
|---|---|---|---|
| 🥉 Bronze | Within its language | TS · HTTP/1.1 | 3 of 4 |
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 | 18 of 71 | 3327 |
Every result
Alpha Round, 14 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 | 1,305,614 | 3.14ms | 8.60ms | 6423.8% | 1.8GiB |
| Connection | Pipelined | 4,096 | 313,124 | 164.31ms | 251.80ms | 6701.9% | 1.8GiB |
| Connection | Short-lived | 4,096 | 1,157,751 | 3.53ms | 12.30ms | 6320.4% | 1.8GiB |
| Concurrency | Async Delay | 32,000 | 991,391 | 32.04ms | 58.50ms | 6330.2% | 6.1GiB |
| Efficiency | Latency-10K | 1,024 | 9,982 | 129.0us | 513.0us | 734.4% | 1.6GiB |
| Efficiency | Latency-1M | 1,024 | 997,443 | 409.5us | 2247.0us | 5236.8% | 2.0GiB |
| Efficiency | Latency-500K/8 | 1,024 | 232,882 | 5333955.8us | 10973184.0us | 773.8% | 352MiB |
| Workload | JSON Comp | 4,096 | 58,990 | 68.32ms | 154.40ms | 6345.2% | 9.6GiB |
| Workload | JSON Comp | 16,384 | 53,102 | 297.67ms | 568.40ms | 6210.2% | 13.0GiB |
| Workload | JSON TLS | 4,096 | 627,740 | 6.54ms | 145.45ms | 6244.1% | 2.7GiB |
| Workload | 8Gbit | 512 | 49,101 | 158.0us | 762.0us | 1093.8% | 1.7GiB |
| Workload | Static TLS | 1,024 | 221,383 | 4.76ms | 39.36ms | 6423.1% | 3.3GiB |
| Database | Async DB | 1,024 | 175,117 | 5.27ms | 36.90ms | 5807.4% | 4.1GiB |
| Database | Fortunes | 1,024 | 49,183 | 17.03ms | 38.60ms | 6407.8% | 4.3GiB |
Compared with
The TS entries around hono-bun on the HTTP/1.1 composite, and the one leading them. The last column shows every profile side by side.
| Entry | Composite | vs hono-bun | |
|---|---|---|---|
| bun | 6065 | +82% | head to head |
| elysia | 4272 | +28% | head to head |
| deno | 2038 | -39% | head to head |
| hono-node | 1867 | -44% | head to head |
Compare hono-bun with any TS entry · Compare hono-bun with any entry, in any language · Every TS entry, ranked
Results updated · How the benchmark is run · The machine · Add or fix an entry