[rabbitmq-discuss] memory usage reporting

Kyle O'Donnell kyleo at 0b10.mx
Wed Apr 24 18:49:46 BST 2013

The difference is actually that my application finished starting using rabbit with R14 whereas with R15 my application didn't get to start because rabbit had reached the high watermark.

Rabbit is not the first erlang app I've seen to use large amounts of Virtual Memory when used with R15.  I am still leaning more towards R15, but haven't found any proof yet.

----- Original Message -----
From: "Matthias Radestock" <matthias at rabbitmq.com>
To: "Discussions about RabbitMQ" <rabbitmq-discuss at lists.rabbitmq.com>
Cc: "Kyle O'Donnell" <kyleo at 0b10.mx>
Sent: Wednesday, April 24, 2013 1:36:36 PM
Subject: Re: [rabbitmq-discuss] memory usage reporting


On 24/04/13 18:13, Kyle O'Donnell wrote:
> So I had a hunch it was erlang R15 so I tried R14 and I am not seeing
> the same behaviour, and my app works just fine:

The status output indicates quite different application behaviour, which 
is more likely the cause of the different output than erlang versions. 
In particular, the previous report showed 1829 open sockets whereas this 
one is only showing 3.

> Does rabbit actually support R15?

Yes, it does. Though I'd recommend going for R16B.



More information about the rabbitmq-discuss mailing list