Releases: centrifugal/centrifugo
v1.7.9
No backwards incompatible changes here.
Fixes
- fix malformed JSON when using empty
info
in connection refresh request - see #214.
Features
- support ACME http_01 challenge using new
ssl_autocert_http
boolean option. Centrifugo will serve http_01 ACME challenge on port 80. See #210 for more details.
Internal
- using Go 1.10.1 for builds
v1.7.8
v1.7.7
No backwards incompatible changes here. This release contains an important fix - if you came across problem when Centrifugo starts leaking memory after a while - this release can solve that case.
Fixes
- fix goroutine leak due to deadlock, see #207
Features
- possibility to set message
uid
via API request - see #205
Internal
- do not send
unsubscribe
messages to client on shutdown - it will unsubscribe automatically on disconnect on client side - using Go 1.10 for builds
v1.7.6
v1.7.5
No backwards incompatible changes here.
The only change is using new version of Go for builds (Go 1.9.2). This will allow to analize performance profiles more easily without having to use binaries. See this new wiki page about investigating performance issues.
v1.7.4
No backwards incompatible changes here.
This release is centered around internal refactoring to detach node from server - see more details in #186.
Features
- optionally create PID file using
--pid_file
command line option. - create connections in separate goroutines to slightly improve GC (and therefore reduce memory usage).
Internal (for developers/contributors)
- Using Go 1.8.3 for builds
v1.7.3
No backwards incompatible changes here.
This release built using new version of Go - 1.8.1, previously Centrifugo used Go 1.7.5, so here we benefit from Go evolution improvements - the most notable is improvements in GC pauses which should in turn improve Centrifugo latency. It also reduces memory usage by about 15-20% when websocket compression enabled.
v1.7.2
No backwards incompatible changes here.
Fixes
- fix reusing read and write buffers returned from connection hijack. This was added in previous release but due to the bug in configuration the feature did not work. Now feature introduced in 1.7.1 should work properly.
v1.7.1
No backwards incompatible changes here.
Fixes
- fix mass resubscribe after several Redis disconnects in a row - more details in #163
Features
- update Gorilla Websocket lib - it now tries to reuse buffers returned from Go http library
hijack
method. We adapted Centrifugo default websocket buffer options to utilize this feature (websocket_read_buffer_size
andwebsocket_write_buffer_size
now0
by default).
v1.7.0
This release changes two important aspects of Centrifugo. We expect that it will be fully backwards compatible with previous one in most scenarios until you were using timestamp
message field in some way.
What's changed
- integration with Gorilla Websocket PreparedMessage for raw websocket. We expect it to drastically improve websocket compression case - reducing both memory and CPU in large fan-out scenarios. This change does not affect SockJS in any way.
timestamp
field removed from message. See #147 for motivation.- Several new memory metrics -
node_memory_heap_sys
,node_memory_heap_alloc
,node_memory_stack_inuse