[rabbitmq-discuss] High Performance Setup Strategy

Mon Feb 18 13:18:57 GMT 2013

Hi,

On 18/02/13 10:53, Florian Müller wrote:
> (Using only one exchange crashes when reaching 64k bindings)

Do you have a crash report or a logfile entry from this crash? If you
can explain the precise nature of the difficulty encountered at this
point then it might apply in the 120k case as well.

> Problem:
> Queues are starting to fill up when reaching 120k Bindings (130-140k
> unique Websocket-Connections). 4-6k delivered Msg/s.

Queues getting longer is not normally a cause for concern, unless your
hardware spec is not sufficient to deal with so many queues when they
get longer. Queues will consume more broker resources when they get
longer. Consider setting a TTL limit to make sure queues don't grow very
long: http://www.rabbitmq.com/ttl.html

Queues getting longer could be a sign that consumers are not able to
keep up, or some other bottleneck between the broker and consumers. Make
sure the network is not saturated.

Do changes to the consumption patterns make any difference to limit for
maximum number of bindings? E.g. What happens when you change the
prefetch count, or switch between server-side and client-side
acknowledgements?

-Emile