Limit to 17 active microphones at once in a room.
Our tests with a top tier Agora client indicate good latency on sparsely populated Agora voice chat rooms, with latency as indicated below.
|Speaker capacity||17||Unlimited (tested to 5,000)|
|Latency on the audience’s client||800ms||400ms|
If the number of users sending streams concurrently exceeds the recommended value, each user in the channel can only see or hear a random group of users who are sending streams. For example, if 18 hosts are sending streams concurrently in a live streaming channel, each user cannot see or hear a random one of the 18 hosts.
Bandwidth: They launch audio streams for each person talking, so after about 10 people making sounds at once, one ends up with 10 audio streams coming in and out of each client
Quality: Google Meet deals with these bandwidth issues by picking winners – which results in a choppy audio experience. Other peer to peer solutions just let latency build causing the ‘frog voice’ problem among others.
Twilio voice is a thin layer on top of WebRTC, with the issues of a peer to peer network combined with a very high cost.