Tests were run against an AWS c5.large instance (2 CPUs with 4GB memory, 2GB allocated to java_heap). We used our RTC, RTSP and RTMP Bee clients to do load testing. Note – connections are added over the course of several minutes.

SUBSCRIBER TESTS

Publishing a 240p (426×240, 200 kbps) stream via RTMP, we were able to achieve the following while still maintaining quality of stream:

• 500 WebRTC subscribers, or
• 1,800 RTSP subscribers, or
• 1,200 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,300 RTSP subscribers, or
• 900 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
• 1000 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:

• 100 WebRTC subscribers, or
• 700 RTSP subscribers, or
• 400 RTMP subscribers

PUBLISHER TESTS

The same server type (2 CPUs with 4GB memory, 2GB allocated to java_heap) can support approximately (tested using the RTCBee Publisher test, RTMP Bee Publisher test and RTSP Bee Publisher test):

Publishing 240p

• 30-40 240p WebRTC publishers, or
• 60-70 240p RTMP publishers, or
• 60-70 240p RTSP publishers

Publishing 480p

• 20-30 480p WebRTC publishers, or
• 60-70 480p RTMP publishers, or
• 50-60 480p RTSP publishers

Publishing 720p

• 15-20 720p WebRTC publishers, or
• 60-70 720p RTMP publishers, or
• 50-60 720p RTSP publishers

Publishing 1080p

• 15-20 1080p WebRTC publishers, or
• 45-50 1080p RTMP publishers, or
• 20-25 1080p RTSP publishers