quic-go
Flagship · Go · standard configuration · completeness 2/4
quic-go, the pure-Go QUIC implementation behind Caddy's HTTP/3, serving HTTP/3 through its http3.Server with default configuration. Handlers are plain net/http ones routed by the Go 1.22 ServeMux; /static reads files from disk on every request and picks the pre-compressed .br/.gz twin off Accept-Encoding. A net/http TLS listener on tcp/8443 answers the harness readiness probe and is idle during the run.
Composite rank
Each profile of a family is worth 1,000 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/3 | 11 of 16 | 331 |
Every result
Alpha Round, 2 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 |
|---|---|---|---|---|---|---|---|
| HTTP/3 | Baseline | 64 | 370,591 | 9.54ms | 33.39ms | 2924.6% | 141MiB |
| HTTP/3 | Static | 64 | 79,661 | 51.17ms | 193.92ms | 1372.5% | 449MiB |
Compare quic-go with any Go entry · Compare quic-go with any entry, in any language · Every Go entry, ranked
Results updated · How the benchmark is run · The machine · Add or fix an entry