[jitsi-dev] Xmpp Server requirements?


#1

Hello,

Is there a simple answer to this complicated question?

What are the server requirements (particularly cpu and bandwidth) for
running a xmpp service that would accommodate 1000 registered
(connected) users and approx. 100 of them engaged in a/v calls?

Settings of the server in question should allow using all Jitsi's cool
features (encryption, a/v, file transfer, sharing....).

thanks

karel


#2

An XMPP server is mostly just an XML router for IM, presence, and
media signaling traffic. The media (audio/video) doesn't go through
the XMPP server. Thus the requirements for a small XMPP service are
not significant (you could probably run this on an old desktop /
laptop, on a standard VPS, etc.). Our Jitsi friends could tell us
whether you would need to also run a media relay (TURN server or
whatever) so that calls always go through, or whether you can use
public relays of some kind.

Peter

- --
Peter Saint-Andre
https://stpeter.im/

···

On 3/28/13 11:41 AM, Karel Novotny wrote:

Hello,

Is there a simple answer to this complicated question?

What are the server requirements (particularly cpu and bandwidth)
for running a xmpp service that would accommodate 1000 registered
(connected) users and approx. 100 of them engaged in a/v calls?

Settings of the server in question should allow using all Jitsi's
cool features (encryption, a/v, file transfer, sharing....).


#3

Thanks Peter.

> Hello,

[...]

Our Jitsi friends could tell us
whether you would need to also run a media relay (TURN server or
whatever) so that calls always go through, or whether you can use
public relays of some kind.

Would I? And what does it take in terms of server resources?

thanks

karel

···

On 03/28/2013 04:38 PM, Peter Saint-Andre wrote:

On 3/28/13 11:41 AM, Karel Novotny wrote:


#4

Hey Karel,

Thanks Peter.

Hello,

[...]

Our Jitsi friends could tell us
whether you would need to also run a media relay (TURN server or
whatever) so that calls always go through, or whether you can use
public relays of some kind.

Would I? And what does it take in terms of server resources?

JingleNodes will probably be your best option here. It is not easy to
predict the resources it would require however, because they depend on
the conversations that are actually going to use the relay, which
depends on many things that you have no control of (such as NAT vendor
market share in the regions where your users are).

That said, JingleNodes only relays packets. There's no transcoding
happening, so it shouldn't be adding much strain on your CPU.

Hope this helps,
Emil

···

On 29.03.13, 16:13, Karel Novotny wrote:

On 03/28/2013 04:38 PM, Peter Saint-Andre wrote:

On 3/28/13 11:41 AM, Karel Novotny wrote:

--
https://jitsi.org