https://www.ejabberd.im/node/5478 en https://www.ejabberd.im/node/5478#comment-58698 <p>Sure. </p> <p>Ejabbered version: I'm using the ejabberd installed by apt-cache on Ubuntu11.04 (apt-cache reports Version: 2.1.5-3+squeeze1build0.11.04.1).</p> <p>Erlang: Also from apt, which reports version: 1:13.b.3-dfsg-2ubuntu3</p> <p>OS and computer specs: I'm running on ubuntu 11.04 on a 4 CPU linux box w/ 16 GB ram and hyperthreading (so it looks like 8 cores to the user).</p> <p>Ethernet is a 1GB ethernet card, but all messages are sent to/from localhost, so none of the messages in question are hitting the network.</p> <p>I can repro this with exactly 1 large message bringing ejabberd up from a clean state. I have two users logged in - one sending and one receiving. We are not saving messages for offline consumption, nor is logging set to verbose. I have max stanza size set to 100MB and I have disabled all shapers. </p> <p>The 'beam' process was using exactly 100% of 1 cpu after the message was sent and finished processing the message approximately 5 minutes later.</p> <p>If I send the same data in 100K chunks it completes in under 3 seconds. This is a workaround we are using now, but it's not idea long-term. We're running our application over BOSH, so we only get two connections at once from the browser. Limiting ourselves to 100K per round-trip with the server over the internet is not ideal.</p> <p>Anything else I can add?</p> <p>Thanks.</p> Tue, 22 May 2012 16:46:14 +0000 braxton comment 58698 at https://www.ejabberd.im https://www.ejabberd.im/node/5478#comment-58686 <p>You're going to have to provide more detail when you ask questions like this.</p> <ul> <li>Which ejabberd version?</li> <li>Which Erlang version?</li> <li>Which operating system and version?</li> <li>What hardware? CPU, RAM, etc</li> <li>Ethernet speed?</li> <li>How many multi-megabyte messages were you sending at the same time, and how frequently?</li> <li>How many online users?</li> <li>When you say 100% CPU, do you mean that all CPUs were at 100%, or just the ejabberd Erlang VM?</li> <li>What was the ejabberd VM's memory consumption?</li> <li>Any other info like this could be helpful.</li> </ul> Sun, 20 May 2012 22:16:51 +0000 emofine comment 58686 at https://www.ejabberd.im