Hi Amir,
for screenshare you need 1.5 Mbit/s on average per stream in the default
config and keep in mind that this is just a recomendation to browsers.
There are peaks when key frames are transmitted, so you'd better
calculate more. As this is a single meeting key frames are transmitted
at the same time to all participants, so peaks add up. If your network
connection is below 1 GBit/s you'll likely run into trouble. 300 MBit/s
should be enough for audio, no screen share and one camera stream in
medium resolution. Keep in mind that clients have to load the HTML5
client when they join. That is competing with media traffic. Check that
clients load the compressed Javascript and CSS assets, that saves 3 MB
traffic per client.
8 cores should be sufficient, RAM may be short. When I did scaling tests
with 2.4.x some time ago I had a machine with 24 GB RAM and 12 vCPUs,
AFAIR RAM was filled up when I reached 500 or 600 participants in a
meeting (don't exactly remember). CPU was never a problem with mediasoup
as SFU. I had 5% bot participants joined with microphone and never got
more than 6 cores busy. Freeswitch was the process which consumed most
CPU cycles.
When network cpacity is getting short on the server weird things are
happening. Media streams are disconnecting and reconnecting over and
over again and the meeting becomes almost unusable.
With 2.4 you'll run into trouble on the clients if many participants
join with more than 4 participants per second, so open up the meeting
early. In 2.5 this is fixed and no longer a problem. If you are running
on 2.4 you might change the lock settings in the meeting so users don't
see each other in the users list. To protect your client from overload
and getting kicked out of the meeting you may close the users list as
long as people are joining.
Kind regards,
Daniel
Am 01.07.22 um 13:55 schrieb amir Kazemi:
> <
https://groups.google.com/d/msgid/bigbluebutton-dev/be479fb4-8840-4bb7-ae63-cdc79e108cden%40googlegroups.com?utm_medium=email&utm_source=footer>.
>
> --
> You received this message because you are subscribed to the
> Google Groups "BigBlueButton-dev" group.
> To unsubscribe from this group and stop receiving emails
> from it, send an email to
bigbluebutton-...@googlegroups.com.
>
> To view this discussion on the web visit
>
https://groups.google.com/d/msgid/bigbluebutton-dev/04e94276-f972-4b5c-abda-0b760e8bad05n%40googlegroups.com
> <
https://groups.google.com/d/msgid/bigbluebutton-dev/04e94276-f972-4b5c-abda-0b760e8bad05n%40googlegroups.com?utm_medium=email&utm_source=footer>.
>
> --
> You received this message because you are subscribed to the Google
> Groups "BigBlueButton-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to
bigbluebutton-...@googlegroups.com
> <mailto:
bigbluebutton-...@googlegroups.com>.
> To view this discussion on the web visit
>
https://groups.google.com/d/msgid/bigbluebutton-dev/ddac746e-7f0c-4332-897a-d9bd3faa8be2n%40googlegroups.com
> <
https://groups.google.com/d/msgid/bigbluebutton-dev/ddac746e-7f0c-4332-897a-d9bd3faa8be2n%40googlegroups.com?utm_medium=email&utm_source=footer>.