We have a very large client (1000+ accounts) that uses it regularly and we have no issues with CPU/RAM. I cannot speak for BW usage, but we dont notice anything major. Of course, they dont have a 1000+ clients in it at once, but they do have regularly meetings etc. using it.

Hi Matt,

Thank you for the note - I was hoping you would say that :-)

You mention it is p2p, is there anything we should be aware of from a firewall perspective? Not on the server side but on the client? Are there any issues with clients behind NAT, how does it negotiate p2p connection if all clients are behind NAT?

Hello,

I did a quick google and got this, https://webrtchacks.com/an-intro-to-webrtcs-natfirewall-problem/
If you go down to "WebRTC tools for NAT/Firewall Traversal", We utilize ICE/STUN to "punch" through the NAT. However, there are cases where the connection cannot be made. 

    This is usually when TURN can kick in, we do not currently support TURN. TURN acts more like a regular media streaming server, this is usually a last ditch attempt as it requires a media server to be "in-the-middle" which uses bandwidth. We've had discussions about implementing a built-in TURN server and it still might, it's on the table.

Thanks again Matt, if TURN support is added it would be useful for it to be an option that could be enabled/disabled. It would be good to stay out of the media path to avoid bandwidth / CPU usage if required.