Hi folks,
I've found this closed issue https://github.com/bigbluebutton/bigbluebutton/issues/11822 and didn't find subject related here, so i ask about !
I've observed the same problem on our install, we can't get more than ~70-90 mic open at the same time and users can't reach after this limit on one server.
From what this could come ?
I'm under bbb version 2.2.33 and some servers are on 2.2.35, we have servers with 12 Vcpu + 16 Go ram (virtualization with OpenVZ).
Is this could come from meetings having more than 40 mic on ?
The ulimit should not be the problem:
$ ulimit unlimited recia@ent-bbb-test[recia](dedicated):~$ ulimit -a core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 31696 max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited open files (-n) 1024 pipe size (512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 31696 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited
From what this could come so ?
I'm running the multipleKurento and I'm on default BBB conf.
Thanks
Julien Gribonvald Développeur Opérationnel Service Logiciels Libres GIP RECIA
What happens as the “error” when you exceed 70?
Is this one meeting or multiple meetings at the same time?
Are these normal users joining from multiple places, or is this an error generated when you run an automated stress test like with bigbluebot
Does this happen on all of your servers, or just some.
I’ve issues with node in 2.2 when you get 400+ users just generally on a server, and there are periods of node pegging the 1core… during this time lots of connection issues, but clears later to work wen few users get off.
Are you using multiuser whiteboard with lots of activity when this occurs.
Freeswitch is just sending 1 stream to everyone, whether 1 or 150 users are joined in full audio, and can handle hundred of streams in a single conference know problem. You can confirm the cpu is low.
Regards,
Stephen
--
You received this message because you are subscribed to the Google Groups "BigBlueButton-Setup" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bigbluebutton-s...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bigbluebutton-setup/d1e81fff-cd44-8c6f-ead7-02ba7150f0f1%40recia.fr.
Commons problems are that users can join the meeting, but they can't connect the microphone in main case and it seems their camera (user don't open the video often so we don't get a lot of bad feedback on this part comparing).
After this problem appear only on load after 200 users per
servers, but we reach audio limitations whereas CPUs aren't on
limits and when around 70-90 mic are open (with only around 60%
CPU used). We had server with 450 users where it worked well, but
on these servers users didn't use a lot the audio and video (from
stats only 40 mic as example and 15-20 video with around 30
rooms). This is only an overview from what the monitoring revealed
and comparing to user bad feedback they provided. So I'm trying to
find a way to avoid these problems, and mainly watching if
something is misconfigured (but as I'm on default conf - expect
for some properties).
For the whiteboard we are in the case of courses, with teachers and students, and in some case meeting for administrative peoples. So it's a normal use I think, I can't say if there is some particular use.
Thanks
To view this discussion on the web visit https://groups.google.com/d/msgid/bigbluebutton-setup/01e601d7376d%24a372c650%24ea5852f0%24%40distancelearning.cloud.