Yeah definitely has to be, the moment I kill it the memory drops back down and it is gradually growing, you can even see it gradually growing in the images.<div><br></div><div>Suhail<br><br><div class="gmail_quote">On Thu, Jul 30, 2009 at 2:41 PM, Matthias Radestock <span dir="ltr"><<a href="mailto:matthias@lshift.net">matthias@lshift.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Suhail,<div class="im"><br>
<br>
Suhail Doshi wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I attached some images that might provide better insight into the problem. You can basically see when everything went down and horribly wrong: memory usage, swap in/out, and load average.<br>
</blockquote>
<br></div>
Is it definitely the rabbitmq server that is busy and eating all the memory, rather than some other process on your system (e.g. the erlang client, python consumers, desktop apps, etc)?<br>
<br>
If it *is* the server, can you observe the memory growing gradually from the start, or does it suddenly spike?<br><font color="#888888">
<br>
<br>
Matthias<br>
</font></blockquote></div><br><br clear="all"><br>-- <br><a href="http://mixpanel.com">http://mixpanel.com</a><br>Blog: <a href="http://blog.mixpanel.com">http://blog.mixpanel.com</a><br>
</div>