Skip to main content

How many threads should I expect from LiveSwitch Client SDK?

Alec Nunez

LiveSwitch Client SDK uses separate threads for each active candidate of a media stream. Every media stream contains a set of on average 5 to 6 candidates and typically every client contains 3 media streams: audio, video, and data. Lastly, we need to determine the number of upload and download connections based on the number of participants and the connection mode being implemented for the call:

 

 

Peer-to-Peer (P2P)

P2P connection mode generates the largest number of upstream and downstream connections and in turn creates the largest number of threads per participant though reduces/eliminates media server load by connecting directly to clients. Using the example diagram above, a P2P call with 4 participants should be expected to generate 90-108 threads.

Selective Forwarding (SFU)

SFU connection mode reduces the upstream bandwidth and client load by only sending one upstream connection to the media server which is then forwarded to all other participants. Using the example diagram above, a SFU call with 4 participants should be expected to generate 60-72 threads.

Mixing (MCU)

MCU connection mode reduces both the upstream and downstream bandwidth along with client load by only sending and receiving one upstream and downstream connection from the media server. It is worth noting that this has a large impact in load for the media server though significantly reduces client load which can be especially useful for legacy and resource-constrained devices such as mobile devices. Using the example diagram above, an MCU call with 4 participants should be expected to generate 30-36 threads.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request
Return to top

Articles in this section