<div class="gmail_extra"><br><br><div class="gmail_quote">2012/11/15 Kaushal Panjwani <span dir="ltr"><<a href="mailto:kaushal.panjwani@gmail.com" target="_blank">kaushal.panjwani@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Using a single worker queue seems to do the job, but the volumes we are looking at is approximately 10,000 msg/sec. So my question is if there are any limit on the capacity of single worker queue?</blockquote><div><br></div>
<div>There is and 10,000 msg/s is probably beyond what a single queue can handle on the kind of hardware you get from Heroku</div><div>add-ons.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
And are there any other solution available out of the box for the load distribution which scales automatically with scaling out of workers?</blockquote></div><br>Consistent hashing exchange does what you want but it is not built-in. So to use it, you will likely have to host</div>
<div class="gmail_extra">RabbitMQ on your own:</div><div class="gmail_extra"><br></div><div class="gmail_extra"><a href="https://github.com/rabbitmq/rabbitmq-consistent-hash-exchange">https://github.com/rabbitmq/rabbitmq-consistent-hash-exchange</a></div>
<div class="gmail_extra"><br></div><div class="gmail_extra">That said, with message volumes of that magnitude I suspect that self-hosting will be necessary for other reasons anyway.</div><div class="gmail_extra"><br></div>
<div class="gmail_extra">HTH,<br>-- <br>MK<br><br><a href="http://github.com/michaelklishin" target="_blank">http://github.com/michaelklishin</a><br><a href="http://twitter.com/michaelklishin" target="_blank">http://twitter.com/michaelklishin</a><br>
<br>
</div>