<br><br><div class="gmail_quote">On Thu, Oct 1, 2009 at 2:19 PM, Matthias Radestock <span dir="ltr"><<a href="mailto:matthias@lshift.net">matthias@lshift.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Suhail,<br>
<br>
Suhail Doshi wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
� �Persistent, ack mode <br>
</blockquote>
<br>
in which case 7KHz outbound is quite reasonable. For comparison, I suggest you try transient messages, and no-ack mode.<div class="im"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
So it really does look like rabbitmq is not able to get items to me<br>
fast enough with lots of items backed in the queue.<br>
</blockquote>
<br></div>
You mentioned 200 items, which really isn't a lot.<br></blockquote><div><br></div><div>200 items per second isn't a lot?�</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
How fast is "fast enough"? You have *50* consumers draining from a single queue. No matter how fast rabbit is, if you add enough consumers eventually rabbit won't be able to keep them all busy.<br>
<br></blockquote><div>My expectation is that rabbit should push a new item to my consumer once that consumer has ACKed a message in less than 100ms</div><div>�</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
Regards,<br><font color="#888888">
<br>
Matthias.<br>
</font></blockquote></div><br><br clear="all"><br>-- <br><a href="http://mixpanel.com">http://mixpanel.com</a><br>Blog: <a href="http://blog.mixpanel.com">http://blog.mixpanel.com</a><br>