|
|
| Author |
Message |
|
| Guest |
 Posted: Thu Oct 29, 2009 9:53 pm |
 |
|
|
Guest
|
Has anyone run into any problems "rapid firing" rabbitmqctl to get queue information?
I am developing an application that needs to know if a queue has lost its consumer is as close to real-time as possible...
Post received from mailinglist |
|
|
| Back to top |
|
| Guest |
| Posted: Thu Oct 29, 2009 10:39 pm |
|
|
|
Guest
|
On Thu, Oct 29, 2009 at 02:52:45PM -0700, Jon Bardin wrote:
> Has anyone run into any problems "rapid firing" rabbitmqctl to get queue
> information?
Yes, don't do this. Queues are inspected using high priority msgs.
Firing too many of these in can degrade performance of Rabbit and
actually lead to higher memory usage because all queues have to respond
to the list_queues command, which prevents idle queues from hibernating,
which would free up resources.
That said I can't think of any immediate solutions to your problem -
maybe if you told us a little more about what you were trying to do,
we'd be able to propose a different solution.
Matthew
_______________________________________________
rabbitmq-discuss mailing list
rabbitmq-discuss@lists.rabbitmq.com
http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
Post received from mailinglist |
|
|
| Back to top |
|
|
|
All times are GMT
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum
|
|
|
Digg It
Del.icio.us
Reddit
Facebook
Stumble Upon
Technorati
