[rabbitmq-discuss] RabbitMQ Issues -> Losing confidence in it.

Jason J. W. Williams jasonjwwilliams at gmail.com
Wed Aug 3 18:25:31 BST 2011

What was the configuration of the exchanges (type), queues (type and
flags) and bindings? Also were the queues long-lived or are they being
created and destroyed constantly?


On Wed, Aug 3, 2011 at 11:17 AM, Abhishek K <abhishek.kona at gmail.com> wrote:
> I am using Erlang R12B. The server had around 20GB of Ram.
> There were around 30 queues on the server with the total memory consumption
> calculated with
> $ rabbitmqctl list_queues name memory
> -Abhishek Kona
> Abhishek Kona
> Department of Computer Engineering
> National Institute of Technology
> Karnataka, India
> On Wed, Aug 3, 2011 at 5:21 PM, Emile Joubert <emile at rabbitmq.com> wrote:
>> Hi Abhishek,
>> On 03/08/11 11:15, Abhishek K wrote:
>> > I am running RabbitMQ 2.20 on Debian Lenny (2.6.26).
>> > There was no changes in the code using RabbitMQ, only the usage rate
>> > increased by 20%.
>> You don't mention the version of Erlang you use. It is worth bearing in
>> mind that later versions of Erlang do better garbage collection. Also,
>> how much RAM is installed on the server? You should generally expect
>> that Erlang / RabbitMQ will use as much RAM as it can.
>> You said that the broker uses 11GB RAM and that the queue size was 7MB -
>> how were these figures determined? If that 7MB is distributed across a
>> large number of queues then that is a possible explanation for the high
>> memory usage. If the startup after a clean  shutdown takes an inordinate
>> amount of time then you might have more than 7MB worth of messages on
>> the broker.
>> You should also inspect the results from running all the "rabbitmqctl
>> list_*" commands to make sure your application isn't using up too many
>> resources (e.g. queues or exchanges) on the broker.
>> RabbitMQ version 2.5.1 adds more memory reporting features to the
>> "rabbitmqctl status" command, with a breakdown of where memory is being
>> used. This is not available on version 2.2.0, but it is another possible
>> reason to upgrade.
>> Regards
>> Emile
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss

More information about the rabbitmq-discuss mailing list