When simulcast saves your receiver (and destroys your sender) #webrtc #coding

12 Jan 2026 · 1 min

Watch on YouTube

1:11

Short technical explainer by Tsahi Levent-Levi on device CPU optimization for real-time communications. The speaker outlines five action items (not fully enumerated in this chunk) and focuses on simulcast and scalable video coding (SVC) as approaches to improve video quality without heavily increasing device CPU load. He recommends simulcast or SVC for large group calls; explains simulcast as sending multiple video streams at different bitrates/qualities to an SFU, which selects which stream to forward to each viewer based on criteria including the viewer device's CPU.

Chapters

Hi, my name is Sahil Lewandlevi. I'm the owner of Bloggic Me and WebRTC courses and I'm here to break down real time communications so you don't have to this time we're going to look at five different action items forward to CC CPU optimization on the device. Another thing that we need to look at is simulcast and SVC scalable video coding. These can improve the quality without adding too much CPU into the system. There are places where I wouldn't use them. There are places that I would in large group calls I would definitely use simulcast or svc. Simulcast for example means that I'm going to send multiple video streams towards the sfu, the media server. I'm going to do that at different bitrate and qualities and the SFU is going to decide which bitrate to send to which user, which quality to serve each user based on whatever criteria makes sense and the CPU power of the devices that are viewing is one of these criteria that we need to look at. Go and follow me at Blogic Me. Thank you.