we have installed jitsi meet / VB2 and we have tested it with ~15users on a 2vcpu/4G ram AWS t3.medium instance.
it was working well.
however, with ~50 users it was problematic.
the users didn’t see any videos after around 30users, once the application core dumped.
according to the monitoring the server wasn’t running out of ram, nor the network bandwith, but the cpu was running ~95%
am I right, that the users didn’t see video because of low cpu? (it was just a test)
if we for example choose a c5.large4xl instance with 16vcpu, would it be enough or should we use octo?
to be honest, it’s not clear that octo will help spreading the NETWORK load or the CPU load (or both)?
bonus question: I can’t enable statistics on port 8080 with the configurations below
Add more JVB.
Either via an autoscaling or just provision more so you have 1 Jitsi-meet (+prosody, +jicofo) and N JVB where N >= 1
You can use MUC for this and the Jitsi Meet server will load balance your users across several video bridges.
You still have 1 point of failure: the Jitsi-Meet server, but most of the stress is focussed on the video bridges so having multiple of them is quite important.