[rabbitmq-discuss] Performance Issues on Rabbit MQ , stops responding

Matthew Sackman matthew at rabbitmq.com
Fri Aug 13 10:38:15 BST 2010


On Fri, Aug 13, 2010 at 12:48:44PM +0530, vivek agarwal wrote:
> I am running RabbitMQ Perf tests on my system, and I find that after pushing
> in 1,50,000 messages of 1KB each, the rabbit mq stops responding to more
> enqueues.
> What is more surprising is that, I cannot even dequeue the messages. Thus,
> its as good as saying that rabbit mq broker has stopped responding, although
> the client still allows me to query with list_queues and list_exchanges.

You're using the default branch aren't you? We've changed from using the
AMQP channel.flow for flow control to using simple TCP backpressure. The
advantage is that it works with all clients and avoids very nasty
buffering issues which hit a lot of people in the 1.8.1 release. The
downside is that when activated, it'll block the entire connection to
the client - not just individual channels.

We do try and be nice here - if a connection is not being used for
publishes at all then we don't block it.

> I am using 2GB Ram.

That may not be enough for those tests. Check the rabbit logs and see if
it's complaining about hitting the memory high watermark.

> I think we really need a disk flow persister, or can someone suggest any
> other way to evade this problem?

Err, if you're running from default then you will be using the new
persister. You should find that it'll be pushing messages rapidly to
disk and should eventually recover.


More information about the rabbitmq-discuss mailing list