Send messages to local existing accounts

mfoss — Sun, 18 May 2008 18:08:40 +0000

VasilyP wrote:

For the test I used a simple NET::XMPP based jabber client written in perl. To simulate load I login 50 users, each user is sending a message (about 1000bytes) to a randomly selected opponent once in a second.

Suddenly I found that my server is using all available CPU and near all the memory is used.

The destinations of messages are existing account in the same Jabber server, non-existing accounts in the same server, or purely random?

If your Jabber server is "jabber.localhost" for testing purposes, a realistic test would be to create accounts test1 up to test50, and send messages to a random destination selected in the group: test1@jabber.localhost .. test50@jabber.localhost

If your current script sends messages to purely random JIDs like aaaa01 instead of testXX@jabber.localhost or aaaa01@jabber.localhost, then your clients are sending messages to remote servers like aaaa01, and this forces ejabberd to try to establish connections with remote servers, that in fact do not exist. This isn't a realistic test.

VasilyP wrote:

According to the ‘top’ report the source of the load is a process ‘beam’.

Yes, 'beam' is the erlang machine where ejabberd runs.

50 users sending each one 1 message every second to another local user should consume very few resources.

You can check the tools I used some years ago to stress test ejabberd: Benchmarking Jabber/XMPP Servers with Jabsimul.

ejabberd - Comments for "Beam process taking all resources"

Send messages to local existing accounts