hanami
Flagship · Ruby · engine: Puma · standard configuration · completeness 4/4
Hanami 2.3 actions and router on Puma, one worker per core. Routing and params through the Hanami API, JSON generated per request, gzip through Rack::Deflater.
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 | 63 of 63 | 1 |
Every result
Alpha Round, 1 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 |
|---|---|---|---|---|---|---|---|
| Efficiency | Latency-1M | 1,024 | 80,703 | 9229501.8us | 18276352.0us | 5810.4% | 2.8GiB |
Compared with
The Ruby entries around hanami on the HTTP/1.1 composite, and the one leading them. The last column shows every profile side by side.
| Entry | Composite | vs hanami | |
|---|---|---|---|
| h2o-mruby | 1856 | +154533% | head to head |
| rack-falcon | 372 | +30858% | head to head |
| rack-iodine | 298 | +24775% | head to head |
Compare hanami with any Ruby entry · Compare hanami with any entry, in any language · Every Ruby entry, ranked
Results updated · How the benchmark is run · The machine · Add or fix an entry