[jitsi-users] Can Jitsi Meet scale to handle larger loads


#1

Hello,

I'm new to Jitsi, and have gotten it up an running on a host machine.
Verry Nice!

The host machine is inexpensive but limited, and I'm interested in
running Jitsi on small inexpensive hardware.

Is there a way of scaling up Jitsi by adding more instances of Jitsi on
more inexpensive hardware.

Thanks,

Richard


#2

Hello,

I'm new to Jitsi, and have gotten it up an running on a host machine.

Congratulations :slight_smile:

Verry Nice!

The host machine is inexpensive but limited

Limited in what way?

Do you mean that it doesn't have much in the way of resources (but you don't
yet know what sort of level of conferencing those resources can support), or
do you mean that you've already run into some limit of how many Jitsi Meet
participants and/or conferences this hardware can support?

I'm interested in running Jitsi on small inexpensive hardware.

That is entirely feasible.

Just for info, are we talking about Raspberry Pies and similar, or something
else here?

Is there a way of scaling up Jitsi by adding more instances of Jitsi on
more inexpensive hardware.

Do you mean:

a) running multiple instances of Jitsi Meet on a single small machine?

If so, why? One server can support multiple conferences with multiple
participants, so why run multiple instances?

b) running one instance of Jitsi Meet per machine on multiple machines?

If so, what are you trying to achieve by this? Have you found a limit for
your particular hardware of the number of participants one machine can
support? I don't *believe* you can scale a conference by inter-connecting
multiple conferencing servers, but I'd be interested from anyone who knows
this is possible.

c) something else?

Maybe tell us more about what you are trying to achieve and what limitations
you're running into; then we can let you know what solutions we are aware of.

Antony.

···

On Wednesday 28 February 2018 at 18:07:05, Richard Geddes wrote:

--
I wish you the worst day of your life today.

After all, then you know the rest will always be better.

                                                   Please reply to the list;
                                                         please *don't* CC me.


#3

The easiest solution for the case that you describe is to install the full Jitsi-Meet suite on one machine (as described in the quick-install document[0]), and then use the second machine only for jitsi-videobridge (the server which handles all audio and video, which consumes the most resources) and connect it to prosody on the first machine. With this setup jicofo will do the load balancing between the two jitsi-videobridge instances.

Regards,
Boris

[0] https://github.com/jitsi/jitsi-meet/blob/master/doc/quick-install.md

···

On 28/02/2018 13:22, Richard Geddes wrote:

I have 2 Atom servers (
https://www.supermicro.com/products/motherboard/ATOM/ICH9/X7SPE-H-D525.cfm
) with 4GB memory. I've installed Jitsi Meet on one, and really don't
know it's limitation, but I was thinking, if I want to expand the
capacity of Jitsi Meet, can I install Jitsi Meet on the other Atom
server, and have them both work together to provide a single service?

I really don't know the capability of Jitsi, but if jitsi is similar to
other services ( databases, web servers, etc ) they eventually move to a
clustered arrangement.


#4

I have 2 Atom servers (
https://www.supermicro.com/products/motherboard/ATOM/ICH9/X7SPE-H-D525.cfm
) with 4GB memory. I've installed Jitsi Meet on one, and really don't
know it's limitation, but I was thinking, if I want to expand the
capacity of Jitsi Meet, can I install Jitsi Meet on the other Atom
server, and have them both work together to provide a single service?

I really don't know the capability of Jitsi, but if jitsi is similar to
other services ( databases, web servers, etc ) they eventually move to a
clustered arrangement.

R

···

On 02/28/2018 12:32 PM, Antony Stone wrote:

On Wednesday 28 February 2018 at 18:07:05, Richard Geddes wrote:

Hello,

I'm new to Jitsi, and have gotten it up an running on a host machine.

Congratulations :slight_smile:

Verry Nice!

The host machine is inexpensive but limited

Limited in what way?

Do you mean that it doesn't have much in the way of resources (but you don't
yet know what sort of level of conferencing those resources can support), or
do you mean that you've already run into some limit of how many Jitsi Meet
participants and/or conferences this hardware can support?

I'm interested in running Jitsi on small inexpensive hardware.

That is entirely feasible.

Just for info, are we talking about Raspberry Pies and similar, or something
else here?

Is there a way of scaling up Jitsi by adding more instances of Jitsi on
more inexpensive hardware.

Do you mean:

a) running multiple instances of Jitsi Meet on a single small machine?

If so, why? One server can support multiple conferences with multiple
participants, so why run multiple instances?

b) running one instance of Jitsi Meet per machine on multiple machines?

If so, what are you trying to achieve by this? Have you found a limit for
your particular hardware of the number of participants one machine can
support? I don't *believe* you can scale a conference by inter-connecting
multiple conferencing servers, but I'd be interested from anyone who knows
this is possible.

c) something else?

Maybe tell us more about what you are trying to achieve and what limitations
you're running into; then we can let you know what solutions we are aware of.

Antony.


#5

I've never played with Prosody before.

I see there are config files in /etc/prosody ( Ubuntu 16.04
installation ):

$0> ll
total 40
drwxr-xr-x 5 root root 4096 Feb 20 22:14 ./
drwxr-xr-x 97 root root 4096 Feb 27 18:16 ../
drwxr-x--- 2 root prosody 4096 Feb 20 22:14 certs/
drwxr-xr-- 2 root prosody 4096 Feb 20 22:15 conf.avail/
drwxr-xr-- 2 root prosody 4096 Feb 20 22:14 conf.d/
-rw-r--r-- 1 root root 353 Jan 30 2016 migrator.cfg.lua
-rw-r----- 1 root prosody 8405 Jan 30 2016 prosody.cfg.lua
-rw-r--r-- 1 root root 292 Jan 28 2016 README

is there a simple template on how/where to add another jitsi
video-bridge to the prosody config files?

I believe that you only need two things in prosody. A second "Component" section like this:
Component "jitsi-videobridge2.example.com"
     component_secret = "abcd"

And making it listen on all interfaces:
component_interface = "0.0.0.0";

On the second machine you can repeat the quick install (with the same domain) and then modify the jitsi-videobridge configuration in /etc/jitsi/videobridge. You will need to update the file named 'config':
Add "--subdomain=jitsi-videobridge2" to JVB_OPTS
Set the correct JVB_HOSTNAME and JVB_SECRET

Hope that helps,
Boris

···

On 28/02/2018 14:10, Richard Geddes wrote:

Richard

On 02/28/2018 02:40 PM, Boris Grozev wrote:

On 28/02/2018 13:22, Richard Geddes wrote:

I have 2 Atom servers (
https://www.supermicro.com/products/motherboard/ATOM/ICH9/X7SPE-H-D525.cfm

) with 4GB memory. I've installed Jitsi Meet on one, and really don't
know it's limitation, but I was thinking, if I want to expand the
capacity of Jitsi Meet, can I install Jitsi Meet on the other Atom
server, and have them both work together to provide a single service?

I really don't know the capability of Jitsi, but if jitsi is similar to
other services ( databases, web servers, etc ) they eventually move to a
clustered arrangement.

The easiest solution for the case that you describe is to install the
full Jitsi-Meet suite on one machine (as described in the
quick-install document[0]), and then use the second machine only for
jitsi-videobridge (the server which handles all audio and video, which
consumes the most resources) and connect it to prosody on the first
machine. With this setup jicofo will do the load balancing between the
two jitsi-videobridge instances.

Regards,
Boris

[0] https://github.com/jitsi/jitsi-meet/blob/master/doc/quick-install.md

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users


#6

I've never played with Prosody before.

I see there are config files in /etc/prosody ( Ubuntu 16.04
installation ):

$0> ll
total 40
drwxr-xr-x 5 root root 4096 Feb 20 22:14 ./
drwxr-xr-x 97 root root 4096 Feb 27 18:16 ../
drwxr-x--- 2 root prosody 4096 Feb 20 22:14 certs/
drwxr-xr-- 2 root prosody 4096 Feb 20 22:15 conf.avail/
drwxr-xr-- 2 root prosody 4096 Feb 20 22:14 conf.d/
-rw-r--r-- 1 root root 353 Jan 30 2016 migrator.cfg.lua
-rw-r----- 1 root prosody 8405 Jan 30 2016 prosody.cfg.lua
-rw-r--r-- 1 root root 292 Jan 28 2016 README

is there a simple template on how/where to add another jitsi
video-bridge to the prosody config files?

Richard

···

On 02/28/2018 02:40 PM, Boris Grozev wrote:

On 28/02/2018 13:22, Richard Geddes wrote:

I have 2 Atom servers (
https://www.supermicro.com/products/motherboard/ATOM/ICH9/X7SPE-H-D525.cfm

) with 4GB memory. I've installed Jitsi Meet on one, and really don't
know it's limitation, but I was thinking, if I want to expand the
capacity of Jitsi Meet, can I install Jitsi Meet on the other Atom
server, and have them both work together to provide a single service?

I really don't know the capability of Jitsi, but if jitsi is similar to
other services ( databases, web servers, etc ) they eventually move to a
clustered arrangement.

The easiest solution for the case that you describe is to install the
full Jitsi-Meet suite on one machine (as described in the
quick-install document[0]), and then use the second machine only for
jitsi-videobridge (the server which handles all audio and video, which
consumes the most resources) and connect it to prosody on the first
machine. With this setup jicofo will do the load balancing between the
two jitsi-videobridge instances.

Regards,
Boris

[0] https://github.com/jitsi/jitsi-meet/blob/master/doc/quick-install.md