Hi guys,
Are there any ideas about using a single RTCPeerConnection instead of using one RTCPeerConnection per user/client? It might be the solution for reducing CPU usage on client side as well as allowing for massive users in a conference room (300++). Has this been on the table before?
Seems like it was discussed here https://bloggeek.me/webrtc-rtcpeerconnection-one-per-stream/ but it was in 2017 and may not be relevant to current Jitsi Meet.
Regards,
Anthony Garcia