I thought I might provide some feedback from experience.
I really appreciate the work that @damencho and the Jitsi team are putting in, my team is looking hopefully try to finally contribute back to their great work by investigating how to have OCTO run using a user load-balanced model, which is currently possible if you aren’t using OCTO. If you need to use geographic load balancing you can only currently do server-based load balancing.
My team is using a 7 region OCTO deployment.
West US, East US, West Asia, East Asia, Europe, South America, Australia
We have a very stable build now.
We have a separate server for running jicofo, prosidy etc (this is a t3.medium) and we use c5n.xlarge for JVBs setup with autoscaling based on CPU usage.
We swapped this from network, because network usage is fairly bursty while CPU usage grows more linearly with the number of participants.
We run 2 modes for usage.
50 users in a Last-12 mode.
100 users in a Last-2 mode.
We have chosen 50 users on Last-12 based on experience from users plus testing results. 50 users on Last-12 results in a decent utlisation of end user cpus any higher than last-12 starts to use significant processing power and bandwidth. 50 person Last-12 conference will use ~ 1GB/sec bandwidth on your server. Hence the need for using network optimised c5n instead of the standard C5.
A 70 person Last-2 conference runs < 1GB/sec for your server (largest session we’ve actually had)
This will use about 80% of the c5n.xlarge CPU however.
Our experience says in Last-12 mode. Max participants is 50 using a c5n.xlarge (a c5.xlarge will sometimes run out of available network when network bandwidth spikes)
Last-2 mode. Max participants is 100 using a c5n.xlarge (the c5n.xlarge will run out of CPU usage at this point)
Note: because some of the considerations are actually the end users device, the reduction of video streams is partly to save their machines. We have also switched off the visual audio monitor too, as there were other reports from other threads around this being a problem. This is also really important to do, as your end user machines won’t support this.
(see - .High CPU utilization on client end)
Also of note, we also completely block all browsers that do not simulcast (eg. firefox) the lack of simulcast significantly disrupts large conferences due to the increased bandwidth consumption.
.