XRCLOUD uses Mediasoup as the WebRTC server and employs the SFU method.
Utilizing the SFU approach of Mediasoup’s WebRTC, the relay server ends up using network bandwidth proportional to the square of the number of users (n2).
(n2)(n^2)
In a single XRCLOUD space, users synchronize data using WebRTC technology through the SFU method. This causes the WebRTC server to send identical data to all users, utilizing outbound bandwidth. If every user turns on their microphone and sends data, the number of connections on the WebRTC server grows quadratically, leading to 625 connections for 25 users, consuming the bandwidth of the WebRTC (Dialog) server. The most problematic aspect is the voice signal.
There are also some issues on the Android side of WebRTC.
Resource Consumption: 0.02 cores and 2 MB of memory and network bandwidth per user.
While there are ways to address the concurrency issue, the following operational method is also available:
Operation Plan for Events with 1000 Participants Across 11 Rooms