Release 10.0.0 Server Performance Metrics
Multiple tests were run against an AWS c5.large
instance (2 CPUs with 4GB memory, 2GB allocated to java_heap) running on Ubuntu 20.04. We used our RTC, RTSP and RTMP Bee clients to do load testing. The following are the average max connection counts, when CPU is observed to be over 80%. Note – connections are added over the course of several minutes in these tests. If connections are added all at once, they may cause a CPU spike which can crash the server.
SUBSCRIBER TESTS
Publishing a 240p (426×240, 200 kbps, 15fps) stream via RTMP, we were able to achieve the following while still maintaining quality of stream:
- 400 WebRTC subscribers, or
- 1,600 RTSP subscribers, or
- 1,000 RTMP subscribers
Publishing a 480p (854×480, 500kbps) stream via RTMP, we were able to achieve the following while still maintaining quality of stream:
- 350 WebRTC subscribers, or
- 1,400 RTSP subscribers, or
- 850 RTMP subscribers
Publishing a 720p (1280×720 1,500kbps) stream via RTMP, we were able to achieve the following while still maintaining quality of stream:
- 250 WebRTC subscribers, or
- 900 RTSP subscribers, or
- 700 RTMP subscribers
Publishing a 1080p (1920×1080 4,500kbps) stream via RTMP, we were able to achieve the following while still maintaining quality of stream:
- 150 WebRTC subscribers, or
- 700 RTSP subscribers, or
- 370 RTMP subscribers
PUBLISHER TESTS
The same server type (2 CPUs with 4GB memory, 2GB allocated to java_heap) and OS (Ubuntu 20.04) can support approximately (tested using the RTCBee Publisher test, RTMP Bee Publisher test and RTSP Bee Publisher test):
Publishing 240p
- 30 240p WebRTC publishers, or
- 60 240p RTSP publishers, or
- 70 240p RTMP publishers
Publishing 480p
- 30 480p WebRTC publishers, or
- 60 480p RTSP publishers, or
- 60 480p RTMP publishers
Publishing 720p
- 30 720p WebRTC publishers, or
- 50 720p RTSP publishers, or
- 55 720p RTMP publishers
Publishing 1080p
- 30 1080p WebRTC publishers, or
- 40 1080p RTSP publishers, or
- 40 1080p RTMP publishers