Implementing multi-core (clustering) in SFU

[hem...@kortobaa.com]

Hello, 

I'm using Medooze SFU to build a room with 100+ participants and using Nodejs cluster & Redis to share data between clusters, but I'm stuck on the endpoint step, how I can create an endpoint for the same room in another Nodejs cluster??

Am tested a room with 100 participants, but the CPU reached the max after 40 participants, cuz the endpoint working on 1 core, my server has 8 cores

Any idea of how I can duplicate endpoint throw multi-core or sharing incoming/outgoing streams data throw multiple endpoints??

am using SFU example

https://github.com/medooze/sfu

[Sergio Garcia Murillo]

You just need to create one endpoint per CPU core and load balance the participants between them.

Would be interesting to capture a flamegraph of the running SFU at max load before and after the change for comparing the CPU usage and detect potential bottlenecks (it doesnt affect the running conferences) :

https://github.com/brendangregg/FlameGraph#1-capture-stacks

Best regards

Sergio

--
You received this message because you are subscribed to the Google Groups "medooze" group.
To unsubscribe from this group and stop receiving emails from it, send an email to medooze+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/medooze/9e1f9ad0-366f-4142-9f57-bf922ad95990n%40googlegroups.com.

[hem...@kortobaa.com]

Sergio,  Thank you for the quick reply ^^

Now I already implemented endpoint per CPU core, but am stuck on another point, when another user joining the room new outgoing stream will create for other participants in the room, but the outgoing streams need to attach to the new participant's incomingstream

Am just saw your code & saw you get video/audio tracks from incoming stream to attach to the outgoing, but Redis can't share objects with functions/methods

Here we go, any idea of how I can share incoming stream using Redis pubsub to other endpoints 

Sergio, Thank you so much for your support ^^

[Sergio Garcia Murillo]

You can send data between streams in different endpoints setting up aew transports + incoming/outgoing streams  in the same way that you do with a browser.

Best regards

Sergio

To view this discussion on the web visit https://groups.google.com/d/msgid/medooze/07c3451c-ce54-46b8-82d0-44ba825b6241n%40googlegroups.com.

[hem...@kortobaa.com]

Thanks for your time Sergio, but I have some questions

1- You mean sending data between streams by using SDP ?? or get StreamInfo from an incoming stream ??

2- After getting data in another endpoint, I need to create a new incoming stream in another endpoint to attach to the outgoing stream ??

3- Can you tell me a small example of these steps like .... "create an incoming stream,  get stream info, etc"

[Sergio Garcia Murillo]

El jue., 10 dic. 2020 16:17, hem...@kortobaa.com <hem...@kortobaa.com> escribió:

Thanks for your time Sergio, but I have some questions

1- You mean sending data between streams by using SDP ?? or get StreamInfo from an incoming stream ??

you can do either of them

2- After getting data in another endpoint, I need to create a new incoming stream in another endpoint to attach to the outgoing stream ??

exactly 

3- Can you tell me a small example of these steps like .... "create an incoming stream,  get stream info, etc"

no, I dont have anything public, sorry

To view this discussion on the web visit https://groups.google.com/d/msgid/medooze/a2420ba4-c924-4a39-9643-69c49e09c07en%40googlegroups.com.

[hem...@kortobaa.com]

Thank you  Sergio for your helping

Now after I got SDP in another endpoint, am created new transport then set the local/remote properties, and created an incoming stream 

After that, I created an outgoing stream and attach it to the newly incoming stream, but I got an empty stream on the client-side.

I think I missed something here, can you help me, please

[Sergio Garcia Murillo]

That should be it, enable more blogs level and chech the stats of each stream to double check where media is Boeing stopped

To view this discussion on the web visit https://groups.google.com/d/msgid/medooze/b1a28feb-f41a-49fb-85d2-a751de9c6fban%40googlegroups.com.

[hem...@kortobaa.com]

Am tested everything in another endpoint but this won't work, can you help me, please

These are my steps after creating a new endpoint & get SDP info

• const offer = SDPInfo.parse(data.sdp);
• const transport = this.endpoint.createTransport(offer);
• transport.setRemoteProperties(offer);
• let answer = offer.answer({

              dtls: transport.getLocalDTLSInfo(),

              ice: transport.getLocalICEInfo(),

              candidates: this.endpoint.getLocalCandidates(),

              capabilities: this.capabilities,
  });
•  transport.setLocalProperties(answer);
  
• incomingStream = transport.createIncomingStream(offer.getFirstStream())
• participant.addStream(incomingStream)

[hem...@kortobaa.com]

Another question, please, when I transfer SDP to another endpoint, which SDP you talk about??

The SDP received from the client or SDP from the endpoint.createOffer?? or Streaminfo from the created incoming stream in first endpoint ??

[leeo...@gmail.com]

there is a demo  https://github.com/notedit/webrtc-broadcast 

[hem...@kortobaa.com]

Thank you so much Leeo ^^ working perfectly