typev
Engine · Type-C · engine: io_uring
TypeV bytecode VM running a Type-C HTTP server.
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.
| Family | Rank | Composite |
|---|---|---|
| HTTP/1.1 | 22 of 34 | 112 |
| WebSocket | 8 of 9 | 90 |
Every result
Alpha Round, 18 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 | 512 | 2,232,140 | 107us | 636us | 6380.0% | 156MiB |
| Connection | Baseline | 4,096 | 2,159,262 | 150us | 729us | 6556.8% | 396MiB |
| Connection | Pipelined | 512 | 44,170,000 | 153us | 608us | 6624.6% | 181MiB |
| Connection | Pipelined | 4,096 | 46,159,084 | 189us | 731us | 6258.8% | 451MiB |
| Connection | Short-lived | 512 | 1,708,478 | 289us | 4.52ms | 6541.8% | 314MiB |
| Connection | Short-lived | 4,096 | 1,674,965 | 2.43ms | 34.40ms | 6595.2% | 472MiB |
| Workload | JSON | 4,096 | 1,227,325 | 2.96ms | 82.00ms | 6396.4% | 720MiB |
| Workload | Upload | 32 | 3,152 | 10.10ms | 27.70ms | 1662.5% | 187MiB |
| Workload | Upload | 256 | 3,053 | 77.28ms | 251.20ms | 3797.3% | 279MiB |
| Workload | Static | 1,024 | 1,123,368 | 25.78ms | - | 6447.9% | 221MiB |
| Workload | Static | 4,096 | 1,130,947 | 68.91ms | - | 6226.6% | 335MiB |
| Workload | Static | 6,800 | 1,123,290 | 31.44ms | - | 6319.4% | 647MiB |
| WebSocket | Echo | 512 | 2,839,865 | 93us | 474us | 6717.4% | 177MiB |
| WebSocket | Echo | 4,096 | 2,738,284 | 140us | 639us | 6294.2% | 464MiB |
| WebSocket | Echo | 16,384 | 2,681,888 | 160us | 1.02ms | 6185.7% | 818MiB |
| WebSocket | Echo Pipelined | 512 | 18,372,604 | 146us | 135us | 6378.4% | 182MiB |
| WebSocket | Echo Pipelined | 4,096 | 18,343,548 | 219us | 458us | 6309.3% | 458MiB |
| WebSocket | Echo Pipelined | 16,384 | 18,274,678 | 386us | 2.74ms | 6083.0% | 362MiB |
How the benchmark is run · The machine · Add or fix an entry