go-websocket
Emerging · Go · engine: net/http · tuned configuration
Go WebSocket echo server using gobwas/ws
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 |
|---|---|---|
| WebSocket | 23 of 25 | 257 |
Every result
Alpha Round, 3 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 |
|---|---|---|---|---|---|---|---|
| WebSocket | Echo | 512 | 964,703 | 406us | 5.83ms | 5206.1% | 93.3MiB |
| WebSocket | Echo | 4,096 | 1,089,321 | 3.43ms | 37.10ms | 5660.4% | 194.5MiB |
| WebSocket | Echo | 16,384 | 1,032,459 | 8.61ms | 54.00ms | 5415.4% | 516.1MiB |
Compare go-websocket with any Go entry · Compare go-websocket with any entry, in any language · Every Go entry, ranked
Results updated · How the benchmark is run · The machine · Add or fix an entry