Start multiple copies of the same program as different processes or<br>threads, and have them each bind to the same queue. The default<br>RabbitMQ behavior seems to be a round robin as to which process<br>gets the next message.<br>
<br>This assumes that the messages on the queue can be processed in an<br>'embarrassingly parallel' sort of way.<br clear="all"><br>Thanks,<br><br>- Jim<br><br>Jim Irrer <a href="mailto:irrer@umich.edu">irrer@umich.edu</a> (734) 647-4409<br>
University of Michigan Hospital Radiation Oncology<br>519 W. William St. Ann Arbor, MI 48103<br>
<br><br><div class="gmail_quote">On Tue, Feb 22, 2011 at 12:43 PM, Rajat Vig <span dir="ltr"><<a href="mailto:rajat.vig@gmail.com">rajat.vig@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div>Hi<br></div><div><br></div><div>We've written an application using the amqp gem with RabbitMQ.</div><div>Currently the bottleneck we've run into is that if there are too many message incoming then processing the queue takes long.</div>
<div>After reading some messages on the list, I think allowing multiple consumers is the way forward.</div><div><br></div><div>How do I do that? And are there any pitfalls/gotchas?</div><div><br></div><font color="#888888"><div>
-Rajat</div>
</font><br>_______________________________________________<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></blockquote></div><br>