Single RTCPeerConnection To Reduce Client CPU

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 but it was in 2017 and may not be relevant to current Jitsi Meet.

Anthony Garcia

well it’s easy to check no ? open 3 connections to and look at chrome://webrtc-internals. Still a single entry. Nothing has changed from this point of view since 2017.

Hmm okay thank you. Seems like I have misunderstood the concept. Thanks again!