On Mon, 28 Sep 2020 at 20:48, Siovel Rodriguez <siove...@gmail.com> wrote: > > Hi maxim, thank you very much for your reply. > > This means you can have up to 200 concurrent users per server? > the most strict restrictions - are from KMS: ~ 200 media streams per server
It depends :(( In case you will have 5 users in the room, each with camera and microphone ON you will get 1 outgoing and 4 incoming streams per user ... 25 total same time: 1 user with audio/video 100 listeners -> 101 KMS stream ... > > Regards. > > El dom., 27 sept. 2020 a las 21:42, Maxim Solodovnik (<solomax...@gmail.com>) > escribió: >> >> Hello, >> >> The logic is here >> https://github.com/apache/openmeetings/blob/master/openmeetings-web/src/main/java/org/apache/openmeetings/web/app/ClientManager.java#L379 >> >> 1) if there is only one node in the cluster - just use it >> 2) if room with users already opened on some node - use it >> 3) find the node with minimum capacity (i.e. sum "room capacity" on every >> node and find minimum) - use it >> >> the most strict restrictions - are from KMS: ~200 media streams per server >> >> On Sat, 26 Sep 2020 at 22:32, Siovel Rodriguez <siove...@gmail.com> wrote: >>> >>> Hi Maxim, we have implemented a cluster of openmeetings in my company as a >>> test. So far it is working fine. I would like to know if openmeetings uses >>> a specific algorithm for load balancing, how many users could it have per >>> room with audio and video and any other details that it could offer me as >>> we intend to put it into production as soon as possible. >>> >>> Greetings >> >> >> >> -- >> Best regards, >> Maxim -- Best regards, Maxim
