[ejabberd] Beam 100% CPU usage
elacour at easter-eggs.com
Sat Jan 9 11:28:56 MSK 2010
On Sat, Jan 09, 2010 at 11:44:22AM +0900, Evgeniy Khramtsov wrote:
> Emmanuel Lacour wrote:
> >thought I do not understand really the output and also, at this time
> >ejabberd no longer eats all CPU (few users connected).
> >I will test again on monday, there will be cpu usage as usual, sure.
> I've attached a simple script which I use for problem investigation
> in running ejabberd.
> Just compile it:
> $ erlc stats.erl
> Put the resulting stats.beam in ejabberd's beam directory. When you
> face with that problem again,
> connect to ejabberd node with remsh and run:
> > stats:run(N).
> It will list all processes with more than N messages in mailboxes.
> Typically I start with N = 100.
Thanks, I ran it as now, CPU usage is 100%, with only 10 users
connected, and I got "ok" with any value, only 0 of course returns
list of processes :(
when I run "i()." last column (msgs) is always 0.
What I don't understand is why strace show me that it is continuously
doing memory map/unmap.
More information about the ejabberd