Minor backwards incompatible changes here when using client_user_connection_limit option – see below.
Centrifugo v2.8.0 has many internal changes that could affect overall performance and latency. In general, we expect better latency between a client and a server, but servers under heavy load can notice a small regression in CPU usage.
Improvements:
- Centrifugo can now maintain a single connection from a user when personal server-side channel used. See #396 and docs
- New option
client_concurrency. This option allows processing client commands concurrently. Depending on your use case this option has potential to radically reduce latency between a client and Centrifugo. See detailed description in docs - When using
client_user_connection_limitand user reaches max amount of connections Centrifugo will now disconnect client withconnection limitreason instead of returninglimit exceedederror. Centrifugo will give a client advice to not reconnect.
Centrifugo v2.8.0 based on latest Go 1.15.5
Docker images
docker pull centrifugo/centrifugo:v2.8.0docker pull centrifugo/centrifugo:v2docker pull centrifugo/centrifugo:v2.8docker pull centrifugo/centrifugo:latest