<div>Hi,</div><div><br></div>All the queues were long lived.<div>There was only a single exchange all queues bound to that exchange, all queues were durable.�</div><div><br></div><div>The routing key was an individual string for each queue.</div>
<div><br></div><div>-Abhishek Kona</div><div><div><div><br><div class="gmail_quote">On Wed, Aug 3, 2011 at 10:55 PM, Jason J. W. Williams <span dir="ltr"><<a href="mailto:jasonjwwilliams@gmail.com">jasonjwwilliams@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">What was the configuration of the exchanges (type), queues (type and<br>
flags) and bindings? Also were the queues long-lived or are they being<br>
created and destroyed constantly?<br>
<font color="#888888"><br>
-J<br>
</font><div><div></div><div class="h5"><br>
On Wed, Aug 3, 2011 at 11:17 AM, Abhishek K <<a href="mailto:abhishek.kona@gmail.com">abhishek.kona@gmail.com</a>> wrote:<br>
> I am using Erlang R12B. The server had around 20GB of Ram.<br>
> There were around 30 queues on the server with the total memory consumption<br>
> calculated with<br>
> $ rabbitmqctl list_queues name memory<br>
> -Abhishek Kona<br>
><br>
> Abhishek Kona<br>
> Department of Computer Engineering<br>
> National Institute of Technology<br>
> Karnataka, India<br>
><br>
><br>
> On Wed, Aug 3, 2011 at 5:21 PM, Emile Joubert <<a href="mailto:emile@rabbitmq.com">emile@rabbitmq.com</a>> wrote:<br>
>><br>
>> Hi Abhishek,<br>
>><br>
>> On 03/08/11 11:15, Abhishek K wrote:<br>
>> > I am running RabbitMQ 2.20 on Debian Lenny (2.6.26).<br>
>> > There was no changes in the code using RabbitMQ, only the usage rate<br>
>> > increased by 20%.<br>
>><br>
>> You don't mention the version of Erlang you use. It is worth bearing in<br>
>> mind that later versions of Erlang do better garbage collection. Also,<br>
>> how much RAM is installed on the server? You should generally expect<br>
>> that Erlang / RabbitMQ will use as much RAM as it can.<br>
>><br>
>> You said that the broker uses 11GB RAM and that the queue size was 7MB -<br>
>> how were these figures determined? If that 7MB is distributed across a<br>
>> large number of queues then that is a possible explanation for the high<br>
>> memory usage. If the startup after a clean �shutdown takes an inordinate<br>
>> amount of time then you might have more than 7MB worth of messages on<br>
>> the broker.<br>
>><br>
>> You should also inspect the results from running all the "rabbitmqctl<br>
>> list_*" commands to make sure your application isn't using up too many<br>
>> resources (e.g. queues or exchanges) on the broker.<br>
>><br>
>> RabbitMQ version 2.5.1 adds more memory reporting features to the<br>
>> "rabbitmqctl status" command, with a breakdown of where memory is being<br>
>> used. This is not available on version 2.2.0, but it is another possible<br>
>> reason to upgrade.<br>
>><br>
>><br>
>><br>
>> Regards<br>
>><br>
>> Emile<br>
><br>
><br>
</div></div><div><div></div><div class="h5">> _______________________________________________<br>
> rabbitmq-discuss mailing list<br>
> <a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br>
> <a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
><br>
><br>
</div></div></blockquote></div><br></div></div></div>