[zaksoup]

Discord's voice chats have no apparent upper limit in how many concurrent users they support - they basically say "the upper limit is how many your client device is able to support without crapping out".

I haven't read into this but it seems like they're doing peer-to-peer for audio or the server load is INCREDIBLY efficient, given this.

[Macha]

It's not P2P. Here's a technical overview: https://blog.discord.com/how-discord-handles-two-and-half-mi...

This is observable to still be the case as an end user. When the discord servers are having issues, people's voices become inaudible. This can be resolved by moving the server to a different, less loaded region, even if that region should have worse connectivity to the users in the voice chat. For example, my raid group often have to bounce our server from Europe to the US to workaround reliability issues on the EU servers.

[gcblkjaidfj]

> It's not P2P. Here's a technical overview

> link describe a P2P WebRTC implementation

what am i missing?

edit: found it. they use a SFU forwarder. That's the cheap version of going full centralization (MCU) benefits. they probably have a better deal on bandwidth than CPU to justify that, or all their use cases work fine with only one person transmitting at once, which gives you the same benefit of a MCU with less cpu usage...