3 ms·
The problem is that webrtc is a very intensive CPU ( each connection have its own encription ). How many users can this solution handle per server?
by fabioyy 7y ago
The problem is that webrtc is a very intensive CPU ( each connection have its own encription ).
How many users can this solution handle per server?
- ec109685 7y agoHow is encryption expense different from normal https streaming from a cdn?
- est 7y agomost https connections are ephemeral and limited to connections per domain. WebRTC can spawn large number of p2p connections.
- fabioyy 7y agopacket size of webrtc(rtp) is VERY VERY VERY small, and since they are UDP, each individual packet must be encrypted. ( i can't just encode a big chunk of data and send to the network like tls ). in fact, for scaling a solution that uses "near realtime broadcast", you probably don't want encryption at all. ( afaik you can't disable webrtc encryption. ) in my tests i can get 3x more performance just using rtmp/rtsp. ( ~8000 video streaming connections on a aws c5.xlarge at 800kbit/s ).
- maxmcd 7y agoIt looks like they support RTMP and a few other streaming methods. Maybe it's just WebRTC for ingress and then it converts to other formats. Given the advertised 500ms of latency I imagine it's not WebRTC->WebRTC.