[ejabberd] ?==?utf-8?q? ?==?utf-8?q? ?= Beam consumes > 400% CPU - why

Michael Vogel icarus at dabo.de
Mon Mar 5 18:46:08 MSK 2018

Am Montag, 05. März 2018 16:03 CET, Holger Weiß <holger at zedat.fu-berlin.de> schrieb: 
> Ah, sorry:
> 	etop -node ejabberd at localhost -sort reductions
> (Or whatever node name you're using instead of ejabberd at localhost -- see
> "ejabberdctl status".)

That's crazy:

# ejabberdctl status
The node ejabberd at manitu is started with status: started

#etop -node ejabberd at manitu -sort reductions
Erlang/OTP 19 [erts-8.2.1] [source] [64-bit] [smp:6:6] [async-threads:10] [kernel-poll:false]

Eshell V8.2.1  (abort with ^G)
(etop at manitu)1> Error Couldn't connect to node ejabberd at manitu 

It is a server with multiple domains - does this matter?


More information about the ejabberd mailing list