[ejabberd] What's involved in fixing memory usage issues with SSL/TLS?

Evgeniy Khramtsov xramtsov at gmail.com
Tue Nov 18 14:31:52 MSK 2008

Jeffrey Rogiers wrote:

>On our server with over 3GB of ram, ejabberd dies with just over 5,000
>users. Meanwhile with TLS off I can have well over 40,000 users online
>with no problem.

I don't know why you have that strange memory consumption, but here are 
my results of benchmarking:

ejabberd on the cold start: 241m/152m
10k without tls: 607m/466m
10k with recent tls (from the svn): 1082m/727m
10k with old tls: 1295m/860m

I'm using Tsung (w/o starttls): connect -> legacy-auth -> roster-get -> 
System: 2 x Intel Xeon 3.00GHz / 8Gb of RAM / Debian Lenny
Erlang R12B-3
ejabberd options: ERL_FULLSWEEP_AFTER=0 ERL_MAX_ETS_TABLES=30000 
ERL_MAX_PORTS=132000 /usr/bin/erl +P 200000 +K true +MHmmmbc 1000 
+MEmmmbc 1000 +MBmmmbc 1000 -mnesia auto_repair

Evgeniy Khramtsov, ProcessOne.
xmpp:xram at jabber.ru.

More information about the ejabberd mailing list