Repository navigation
v0.5.9
A smaller worker, timers on time, and WebSockets up to max_conns. Goose v2026.3,
goose-hash v0.0.4, goose-tls v0.0.5, and goose-compress v0.1.4.
Changed:
- The loops' timers fall due by the precise monotonic clock on Linux and macOS, not
the coarse one, which is up to a scheduler tick old:/delay/10at 64 connections
answered in 12.2 ms, and now in 10.2 ms
(decisions). - A timer table adds its cells as timers need them, up to its capacity, rather than
writing every cell at open, and a box's table of live keys is left ascalloc
zeroed it. A worker withmax_waitingatmax_conns, 16,384, held about 0.8 MiB
before its first wait; now it holds what its waits use. Config.ring_buffersis 64, down from 256: io_uring writes every provided buffer
in turn, so each worker held 1 MiB of them at any load, and 64 serve as fast on
Linux (decisions). On Windows, IOCP
serves 1 to 7% fewer requests a second with 64; a program there that wants them
back setsring_buffers: 256.- A WebSocket is promised bytes of the gather budget only while it holds part of a
message, a message in fragments or a frame split across reads, not from its upgrade
on. Idle connections and messages that arrive whole cost no budget, so a worker holds
as many WebSockets asmax_connsallows, where the defaults stopped it at 1,021.
ws_upgradeno longer answers 503; a message the budget can't hold closes its
connection with 1013 (Try Again Later)
(decisions).
Removed:
http::ws_admit. A program that called it beforews_switchdrops the call; its
WebSockets are then promised their bytes asws_upgrade's are.