pedestal
Emerging · Clojure · engine: Jetty · standard configuration · completeness 4/4
Pedestal connector-map benchmark entry using the standard Jetty-backed 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, 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 | 62 of 63 | 23 |
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 | 327,026 | 5932812.2us | 12537856.0us | 5522.0% | 4.4GiB |
Compared with
The Clojure entries around pedestal on the HTTP/1.1 composite, and the one leading them. The last column shows every profile side by side.
| Entry | Composite | vs pedestal | |
|---|---|---|---|
| ring-http-exchange | 2986 | +12659% | head to head |
| ring-jetty9-adapter | 1564 | +6582% | head to head |
| http-kit | 390 | +1566% | head to head |
Compare pedestal with any Clojure entry · Compare pedestal with any entry, in any language · Every Clojure entry, ranked
Results updated · How the benchmark is run · The machine · Add or fix an entry