<div dir="ltr">Hi there ,<div><br></div><div>I have tried to with multiple producer and multiple consumer since my producer and consumer are single threaded (around 10 each) but it's the same statistics in test-1, which is around 5000 msg/sec. And since eventually we will use python clients in real application of rabbitmq, I think it would be good to know how it behaves with python clients ( in this case I chose python-pika).</div>
<div><br></div><div>//P</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Aug 1, 2013 at 9:14 PM, Michael Klishin <span dir="ltr"><<a href="mailto:mklishin@gopivotal.com" target="_blank">mklishin@gopivotal.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Priyanki Vashi:<br>
<div class="im"><br>
> So from this it feels that maximum capacity of a single node of type DISK is limited to 5000 msg/sec when publisher confirm and consumer ack is enabled in this version. I thought main reason for this could be server latency. Is it correct understanding or I am missing something here to consider ?<br>
<br>
</div>If you say your producer maxes out one core, you are limited by Pika's throughput (for which 5K/s<br>
from a single process sounds about right).<br>
<br>
Try with a multi-threaded Java producer (allowing the JVM use as many<br>
cores as you have publishing threads is a good idea) or multiple Pika producer processes.<br>
--<br>
MK<br>
<br>
<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></div>