...

-Xmx16g
-Xms16g

Besides, if REST hooks monitoring functions in WCS web  interface are not used, the work with memory may be optimized by switching off the interaction between WCS core and WCS manager with the setting in flashphoner.properties file

disable_manager_rmi=true

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

rest_max_connections=200

To escape thred poolexhausting and deadlocks this value should be reduced, for example

rest_max_connections=20

If REST hooks are not used, REST client can be disabled with the following parameter

disable_rest_requests=true

UDP tuning

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

...