Server default settings are mostly universal and need to be tuned to certain client case.
REST client tuning
When REST hooks are used, on every WCS server action (establishing client connection, publishing and playing a stream, making a SIP call etc) HTTP REST connection to backend server is established. With a large number of simultaneously publishing clients or subscribers, with the default WCS settings it is possible to exhaust the WCS REST client thread pool, that is lead to deadlocks. Then, server stops to publish and play streams.
By default, a maximum number of simultaneous REST connections is set to 200 with the following parameter in flashphoner.properties file
To escape thred poolexhausting and deadlocks this value should be reduced, for example
If REST hooks are not used, REST client can be disabled with the following parameter
Excessive logging supression
When REST hooks are used, REST client operations, EchoApp default backend operations and REST API server operations are written to WCS core logs. That leads to large number of entries in the log file and, therefore, inceases the server load. The excessive logging may be decreased if necessary using the following parameters in log4j.properties file:
Streaming mediadata are transferred with UDP packets. Those packets can be dropped, for example if server does not have enough time to parse packet queue, that leads to picture quality loss and freezes. To escape this it is necessary to tune UDP sockets buffers with the following settings in flashphoner.properties file
and to tune system queues with command
To diagnose UDP problem, it is necessary to track UDP packets dropping with command
Channel load optimization
Users' playback picture quality depends on bitrate: the higher the bitrate, the higher the quality. However, the higher the bitrate, the higher data transfer channel load and, if the bandwidth between the server and clients is limited, there is a possibility that the channel will be fully loaded. This leads the bitrate dropping and a sharp decline in quality.
In this regard, it is necessary to limit the bitrate to ensure sufficient picture quality with an acceptable channel load.
Publisher bitrate limiting
Server bitrate limiting
Minimum and maximum bitrate values in bps on server may be set with the following parameters in flashphoner.properties file
To exclude fast bitrate rise bu=y browser, the following parameter should be set
Stream decoding on demand only must be switched on to reduce server load:
Changing dynamic ports range in Linux
Dynamic or ephemeral port is a temporary port that is opened when establishing IP-connection from certain range of TCP/IP stack. Many Linux kernel versions use ports range 32768 — 61000 as dymanic ports. Enter the following command to check what range is used on server
If this range overlaps with WCS standard ports, it should be changed with the following command
Adjusting the maximum number of opened files
Legacy settings (before build 5.2.762)
In the launch script
webcallserver that is in subfolder
bin in WCS home folder, for example
start() function the maximum number of opened files is set
By default, this value is set to 20000, but it may be increased if necessary, following the limitations of the operating system used.
Using environment variable (since build 5.2.762)
Since build 5.2.762, maximum opened files limit can be set using the following environment variable
in setenv.sh file. When updating WCS from previous builds, this variable should be added to setenv.sh manually, for example
Unlike the webcallserver startup script, the setenv.sh file is not overwritten on subsequent updates, therefore it is not necessary to restore this setting after every update.
Using service parameter while launching from non-root user (since build 5.2.801)
Since build 5.2.801, WCS is launching from 'flashphoner' user for better security. In this case, maximum opened files limit can be set using service parameters
Maximum opened files limit is set with
LimitNOFILE parameter, for example
Traffic encryption in a separate thread for each client session
By default, one CPU thread encrypts medai traffic for all the client sessions. This leads to one CPU core overload by such thread, espacyally on low-power servers, for big subscribers amount. Then, server can not send mediapackets to all subscribers, and streams viewed are degrading, FPS lowering and freezing.
To distribute the load evenly across the CPU cores, it is necessary to enable traffic encryption in a separate thread for each client session with the following parameters
and restart WCS.