[Service] User=flashphoner Group=flashphoner LimitNOFILE=100000 ...
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
rtp_paced_sender=true rtp_paced_sender_initial_rate=200000 rtp_paced_sender_increase_interval=50 rtp_paced_sender_k_up=0.9
and restart WCS.