Hello
1. According our investigation,
Each of such connections takes around of 200 bytes, if it was not publish/play in this connection.
Each of such connections takes around of 30 k bytes, if it had publish/play in this connection.
2. We have found a bug with setting
Code:
keep_alive.algorithm=NONE
When keep alives are disabled, Websocket connection is not released after page reload (for example in Chrome browser).
That's why you have too many open connections indicated.
We have fixed this bug in the
latest server build 2108.
It is under verification now.
3. We have added the new setting in
server.properties
Code:
keep_alive.enabled=websocket,rtmp,rtmfp
This means you can enable / disable keep alives for a protocol.
For example you can enable keep alives for RTMP only:
This setting was also introduced in 2108 and is under verification now.