Back with another stupid question, sorry!
As I understand it, mediasoup workers run on a single thread, and threads are managed by the OS. Is mediasoup overriding this in some way? If not, why create a worker per core?
Back with another stupid question, sorry!
As I understand it, mediasoup workers run on a single thread, and threads are managed by the OS. Is mediasoup overriding this in some way? If not, why create a worker per core?
As the documentation says somewhere, a mediasoup-worker doesn’t run in a thread but in a separate process
Thanks for getting back, yes, it says sub process. But still, processes are also managed by the OS? So my question still seems relevant. Or am I missing something?
Creating a worker per core is just a recommendation and mediasoup does not override process management in any way.
That makes sense from the load tests on a MacMini that we ran the other day. The instantiated worker load did not seem to correlate to the load per CPU. But then M1 has this split between efficiency and performance cores, it was clear the OS made some decisions. Thanks for the clarification!