ejabberd - Comments for "the performance will drop down very fast if client connections exceed 150000"

Does it need to add any

lil — Mon, 29 Jun 2015 11:16:09 +0000

Does it need to add any virtual ips to ejabberd machine ? So that more IPs can be assigned, but if you scale horizontally how the Load balancer is able to handle soo many connections ?

P.S I'm on a way to improve the required skills to scale the machines.

Scalability is not magic and

mremond — Sat, 27 Jun 2015 07:17:00 +0000

Scalability is not magic and requires skills. It is highly dependent on solution design, extension use, features uses, client behavior, ...
Ejabberd is a highly versatile and scalable component, but you have to "design" your overall solution for scalability.

After going with Ejabberd

lil — Sat, 27 Jun 2015 06:34:16 +0000

After going with Ejabberd forums, I choose it for its massive scalability and performance.
But I'm not able to reach close to any of the numbers you folks had posted here.

With the same configuration
cpu: 8core, 16threads
memory: 32GB
Ejabberd : 15.03
Ethernet: big enough

I'm not able to scale more than 33K users and response is at 1-2 sec.
I changed the shaper and ip port ranges, but of no use.

Can someone help me to achieve the good scale numbers of ejabberd.

Well, it is very hard to

mremond — Tue, 24 Mar 2015 17:28:00 +0000

Well, it is very hard to reply performance question without working with you on the platform. Performance need to be design at a broad system level, including clients, backend, etc.
Scaling ejabberd means you need to have a good knowledge of the internal and require some good skills.

Please, note that it also depend on the version you are using. 15.03 is much much more scalable that 2.1 for example.

Hi Guys, Facing the similar

dhinesh.ravi — Mon, 23 Mar 2015 05:53:25 +0000

Hi Guys,

Facing the similar issue. Any improvements?

Thanks,
Dhinesh

Just my 2 cents quickly. I

c0rn0 — Fri, 27 Jun 2014 21:14:30 +0000

Just my 2 cents quickly. I don't have a solution though, BUT I have recently stress tested ejabberd with Tsung and what you are reporting, I've seen pretty much the same thing, that the moment I have more than 140 - 160K clients connected to the ejabberd instance, the CPU usage goes up insanely and the arrivalrate of the subsequent clients goes down substantially.

If you make any progress regarding this in the meantime I would love to hear your tweaks/experiences.

I don't have any feedback

smcracraft — Tue, 24 Jun 2014 23:12:33 +0000

I don't have any feedback since I am less advanced on the testing.

I just got tsung up and running with a very simple xml for basic testing.

It doesn't calculate any statistics of use for seeing if increasing ejabber
server numbers are useful.

May I ask what platform you are using to test and what kinds of statistics
you generate? Are they automatically compiled by your test?