jooby
Flagship · Java · engine: jetty · standard configuration · completeness 4/4
Jooby 3.9 on Jetty in the script API. Routing and path/query values through Jooby's Context, JSON through the Jackson module, gzip through the built-in compression at level 1, json-tls on 8081.
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 | 66 of 70 | 448 |
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-10K | 1,024 | 9,805 | 127.1us | 165.0us | 64.4% | 8.6GiB |
Compared with
The Java entries around jooby on the HTTP/1.1 composite, and the one leading them. The last column shows every profile side by side.
| Entry | Composite | vs jooby | |
|---|---|---|---|
| cardigan | 4285 | +856% | head to head |
| helidon-production | 2208 | +392% | head to head |
| spring-boot | 1242 | +177% | head to head |
Compare jooby with any Java entry · Compare jooby with any entry, in any language · Every Java entry, ranked
Results updated · How the benchmark is run · The machine · Add or fix an entry