About single Router consumers limit and "pipeToRouter"

[zaidiqbal]

Here is the list of topics I followed, they cover scalability deeply enough to get started:

CPU/Bandwidth results for many-to-many rooms in production.

Between 15 rooms with users ranging anywhere from 1 → 11 (currently). Totaling a maximum of 53 viewers, and 27 broadcasters. Results may differ with users just sending audio broadcasts, but setup uses pipetransporting and all sorts for maximum scalability. On 5 servers, CPU usages is at about 2-20%overall CPU usage as displayed in the picture. SPECS: 4vCore @ 8GB RAM (HDD who cares) and 1Gbp/s networking unmetered. [image] Due to my setup and rooms expanding past a single core’s ability,…

How to manage rooms, workers etc when using multiple server/node clustering?

I am using node clusters to divide loads on all cores of cpus, doing the same for socket io using io redis adapter to distribute sockets between cores. Socket will be connected to any of the cores. I am having issue here which is user’s socket gets connected to core 1, while room is on core 2 and workers, producers etc all references are on core 2 as well, so socket can’t access all that stuff of the room he want to join in or to perform any other action because they are on separate process. I…

access workers, routers, transports objects from one node process to another

Is there any way I can access workers, routers, transports objects from one node process to another? I was thinking that may be I can construct object of workers, routers, transports from their respective process ids? I am actually planning to make multiple processes of my app i.e run on all cores of my machine. Now that my workers, routers, transports instances are on one of the processes and I need to access them in another process of my node app? Is their any way I can do that? EDIT: You …

Mediasoup Scaling resource

I’ve been trying to wrap my head around mediasoup scaling and combing through the resources available to understand the constraints. I put this together for my own understanding but if it’s correct, I hope it might also be useful to other people who join the community. I’d appreciate any feedback and also happy to refine this into something more complete, maybe add some diagrams if it’s interesting to people. This information is not the result of benchmarking myself, instead this is a result of…

Maximum number of consumers per worker is 500 w.r.t CPU?

It is mentioned in the official docs here: mediasoup :: Scalability and in discourse topic as well here: A room with 100 participants Does this mean that there is hard limit of 500 for a worker or does this mean that if I use high end server then the same worker can handle more than 500 consumers? I am using AWS instance g4dn.8xlarge which is a high end server and it has 32 cores. I am using 1 worker per call so each call has it’s own worker. I am showing max 20 streams to each participant so…