...And you can do this rate limiting by watching the so called "publisher confirms" (ConfirmSelect).<br><br><div class="gmail_quote">On Thu, Nov 24, 2011 at 2:08 PM, Matthias Radestock <span dir="ltr"><<a href="mailto:matthias@rabbitmq.com">matthias@rabbitmq.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Jeffrey,<div class="im"><br>
<br>
On 23/11/11 21:40, Jeffrey Chen wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I am testing performance on rabbitmq clustering setup. I have 2 nodes<br>
with active/active setup, both nodes write to disk, and they both are in<br>
a local area network. When I start my publisher and consumer, the<br>
publisher is very fast, is it able to send 100000 in few seconds. The<br>
problem is the consumer. My consumer is only able to consume around 500<br>
messages per second.<br>
</blockquote>
<br></div>
Publishing in AMQP is asynchronous. So when a test is measuring the rate at the publisher, one has no idea of the status of those published messages - they could all be sitting in local buffers in the client libraries, or in various network buffers, etc.<br>
<br>
Furthermore, rabbit is designed to cope with producer spikes, but that comes at the cost of reduced consumer rates. So if in your test the producer is simply bombarding rabbit with messages, the consumer rate will be much lower than it would be otherwise.<br>
<br>
For meaningful benchmark results one needs to rate limit the producer.<br>
<br>
<br>
Regards,<br>
<br>
Matthias.<div class="HOEnZb"><div class="h5"><br>
______________________________<u></u>_________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com" target="_blank">rabbitmq-discuss@lists.<u></u>rabbitmq.com</a><br>
<a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/<u></u>cgi-bin/mailman/listinfo/<u></u>rabbitmq-discuss</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Eugene Kirpichov<br>Principal Engineer, Mirantis Inc. <a href="http://www.mirantis.com/" target="_blank">http://www.mirantis.com/</a><br>Editor, <a href="http://fprog.ru/" target="_blank">http://fprog.ru/</a><br>