Besides, if 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
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.