[rabbitmq-discuss] looks like a memory leak, 2.4.1

Daniel Maher dmaher at milestonelab.com
Tue May 3 08:46:05 BST 2011

On Mon, 2011-05-02 at 20:29 +0100, Matthias Radestock wrote:
> Gavin M. Roy wrote:
> > On Monday, May 2, 2011 at 2:48 PM, Matthias Radestock wrote:
> >> The above graph shows system memory usage. It is perfectly normal for a
> >> non-idle linux system to gradually fill up all the memory with cached
> >> files.
> > Which I expect in disk buffers in that graph. The inactive memory is 
> > what threw me, going back and re-reading up on it, this is memory that 
> > previously been allocated in vm that can be reclaimed for other use, 
> > correct?
> I have no idea. Consult your resident Linux expert ;)
> As long as the system is not swapping it is probably fine. Have you ever 
> seen it swap?
> >> And, as you say, rabbit thinks it is only using 330MB. Is the
> >> rabbit Erlang process considerably bigger than that?
> > No, it is in that range.
> In which case it's clearly not rabbit that is using the memory. So don't 
> blame the poor bunny.

We saw exactly this behaviour in our environment as well : steadily
increasing memory usage over time, related to Rabbit virtual memory
usage increasing over time ; however Rabbit real memory usage remained
relatively low.

The culprit in our case was that we had created far too many queues, and
that we weren't clearing them out when they weren't being used.  Once we
started managing this properly (read : architecting our queues more
efficiently, destroying them when not in use) our memory usage plummeted
- real and virtual - plummeted.


Daniel Maher
« can't talk, too busy calculating computrons. »

More information about the rabbitmq-discuss mailing list