Hi Séverin,
Benchmarking is not easy, and there is a very strong tendency for first-time administrators of BigBlueButton -- and even experienced BigBlueButton administrators -- to get it wrong.
For example, see this thread
The above poster had their hear in the right place, but their conclusions were *way* off.
It's interesting to look at how other open source projects handle the questions of "how many concurrent users". For example, in the FreeSWITCH FAQ:
they write
This all depends on your application. You will need to load test with your application to know your limits, your mileage will vary depending on your specific requirements.
Please do not ask this question on the mailing lists as you will always get the same official response from the FreeSWITCH project; "we only perform benchmarking and confirm these results per FreeSWITCH deployment, as each deployment will result in varying figures. Commercial support is available from the project for this task. The project has learned from experience the dangers of entertaining such questions and its policy is to not do so over the free public forum."
We all want to believe that BigBlueButton will scale to large numbers of users, but as developers we're grounded in cold, hard reality. As the FreeSWITCH FAQ points out, "it all depends on your specific requirements".
Based on our development and testing of BigBlueButton over the past four years, we're comfortable enough saying that on a *DEDICATED* *QUAD-CORE* CPU with +2G of memory, BigBlueButton should be able to support 25 concurrent users with *GENERAL USAGE*.
Even the above statement is dangerous as people want just want absolute numbers. There are some that will read the above and think "Thank you Fred. 25 is the minimum number." and proceed to install BigBlueButton alongside their existing web application running on a shared VPS server (not easy to do, but some will eventually figure it out) and then hold a session with 25 user joining from various internet connections, have everyone share webcams, and have the presenter sharing their desktop and slides. When they do try it, they will find it doesn't support 25 concurrent users. (If you read the previous sentence and are thinking 'we'll, it sounds like it should', then your getting a sense of the danger in posting absolute numbers).
For BigBlueButton, we believe the best benchmark is real-world usage. If you've just conducted a session with BigBlueButton for 15, 20, 25, 30, 35, etc. concurrent users and it worked well, then let the community know about it! Give as much information as you can about your hardware, bandwidth, BigBlueButton version, and usage of BigBlueButton during the session.
When your reading such posts, we encourage you to be a bit sceptical and look for holes in their data. Was everyone on a LAN? Was the machine dedicated or virtualized? Did they do the test at 2am in the morning? How many times did they do the test? Did they test a few users and then extrapolate the numbers? Did they restart the server after tests? How did the monitor CPU and bandwidth usage? How did they conclude that the test went 'well' or 'not well'. Did they get feedback from users on their experience? Was the feedback qualitative or quantitate? Etc.
We're not looking for perfect tests (there are none). But with the community sharing their experiences, readers can get a blended sense of BigBlueButton's scalability without the danger of absolute numbers.
To help out, we'll be doing another community stress test of BigBlueButton 0.8 before it's final release, and will share all our results.
Regards,... Fred
--
BigBlueButton Developer
BigBlueButton on twitter: @bigbluebutton