3 ms·
But it's still small compared to YouTube video content served. Also, the WebRTC stuff all browser based videoconferencing apps are built on supports peer to pe
by londons_explore 6y ago
But it's still small compared to YouTube video content served.
Also, the WebRTC stuff all browser based videoconferencing apps are built on supports peer to peer Comms in most cases, so worst case they could have moved all the users over to that in an overload situation.
- jtwaleson 6y agoNot sure about the comparison with YouTube. YouTube is one to many, and can be heavily cached. Meet is many to many with no caching.
- jeffbee 6y agoRight, and YouTube doesn't need high priority traffic because it has a deep buffer on the receiver, whereas videoconferencing will be disrupted by even a single dropped frame.