Scaling Cloudflare Realtime SFU beyond 5–10 active tracks per client, is it even possible?
🌍CDN
REST API❓Other (read rules)
REST API❓Other (read rules)Hi everyone, I’ve been testing Cloudflare Realtime SFU for large interactive audio/video rooms (Twitter Spaces style, 10k+ listeners). Media scales fine, but signaling is a bottleneck, every time active speakers change, you have to send one /tracks/update per session—so 10k calls for 10k listeners. Browsers can’t handle hundreds of idle tracks, so you need dynamic updates.
Is there any way to batch these operations, or is this service basically unusable for setups with more than 5–10 active users per client?
Is there any way to batch these operations, or is this service basically unusable for setups with more than 5–10 active users per client?
Welcome to the official Cloudflare Developers server. Here you can ask for help and stay updated with the latest news
87,353Members
Resources
Similar Threads
Was this page helpful?
