Hi,<div><br></div><div>So I stumbled across this: <a href="http://www.lshift.net/blog/2008/11/14/tracing-python-memory-leaks">http://www.lshift.net/blog/2008/11/14/tracing-python-memory-leaks</a></div><div><br></div><div>I basically keep the channel object and connection open the entire time so I do not do the statup stuff over and over, is this a bad idea? Once the channel has been retrieved, my consumer doesn't deal with it again, it just keeps accept requests from it. I don't see any global objects of mine increasing in size so I can only think I am doing something wrong from a rabbitmq perspective.</div>
<div><br></div><div><div>def connect_consumer():</div><div> consumer = EventQueueConsumer()</div><div> channel = consumer.get_channel()</div><div> </div><div> <a href="http://logging.info">logging.info</a>("Consumer started")</div>
<div> </div><div> while True:</div><div> channel.wait()</div><br><div class="gmail_quote">On Fri, Jul 31, 2009 at 12:33 PM, Suhail Doshi <span dir="ltr"><<a href="mailto:digitalwarfare@gmail.com">digitalwarfare@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">The memory leak is in the consumers, thanks Matthias.<div><br></div><div><font color="#888888">Suhail</font><div><div>
</div><div class="h5"><br><br><div class="gmail_quote">On Thu, Jul 30, 2009 at 4:37 PM, Matthias Radestock <span dir="ltr"><<a href="mailto:matthias@lshift.net" target="_blank">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><br>
<br>
Suhail Doshi wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
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.<br>
</blockquote>
<br></div>
Do you definitely see the rabbit process consuming the memory? How big does it get? And what about CPU usage?<br>
<br>
The reason I am asking is that killing the server also affects the clients, i.e. it is possible that a *client* is consuming all the memory, and releases it as soon as the server connection is severed.<br>
<br>
So please check the *per-process* memory and CPU stats.<br>
<br>
Now, if it really is the server that is eating the memory, please run all the various list_* commands in rabbitmqctl to see whether any of them are showing growth.<br>
<br>
Finally, try publishing messages without marking them as persistent, and see whether that changes the behaviour.<br>
<br>
<br>
Regards,<br><font color="#888888">
<br>
Matthias.<br>
</font></blockquote></div><br><br clear="all"><br></div></div><div class="im">-- <br><a href="http://mixpanel.com" target="_blank">http://mixpanel.com</a><br>Blog: <a href="http://blog.mixpanel.com" target="_blank">http://blog.mixpanel.com</a><br>
</div></div>
</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>