<div dir="ltr">Thanks Michael.<div><br></div><div>The line:</div><div><br></div><div>"<span style="color:rgb(80,0,80);font-family:arial,sans-serif;font-size:13px">Erlang R15B01 (erts-5.9.1) [source] [64-bit] [smp:4:4] [async-threads:0] [kernel-poll:false]"</span></div>
<div><span style="color:rgb(80,0,80);font-family:arial,sans-serif;font-size:13px"><br></span></div><div><span style="color:rgb(80,0,80);font-family:arial,sans-serif;font-size:13px">is from running "erl" on the same VM as the broker.</span></div>
<div><span style="color:rgb(80,0,80);font-family:arial,sans-serif;font-size:13px"><br></span></div><div><font color="#500050" face="arial, sans-serif">Regarding the suggestion of "</font><span style="font-family:arial,sans-serif;font-size:13px">RABBITMQ_ALLOW_INPUT=true", this is a bit tricky for me to run. For starters, this is a Rabbit instance running in a production environment so I can't easily restart it. And even if I could, the way we start RabbitMQ is a bit quirky (long story).</span></div>
<div><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><div><span style="font-family:arial,sans-serif;font-size:13px">Is there some way to get the aysnc-threads value from a "rabbitmqctl eval..." or from the logs? I do have ready access to those.</span></div>
<div><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><div><font face="arial, sans-serif">A few of the messages are persistent, but the vast majority of them are non-persistent. Our disk I/O on the box looks relatively low. Many intervals of 0 reads/writes with occasional blips up, but noting particularly heavy.</font></div>
<div><font face="arial, sans-serif"><br></font></div><div><font face="arial, sans-serif">Also, we are running this in a cluster with another box, with all queues in HA mode. I imagine that would have some overall CPU impact, but don't see why it would concentrate everything on one core.</font></div>
<div><font face="arial, sans-serif"><br></font></div><div><font face="arial, sans-serif">Thanks again,</font></div><div><font face="arial, sans-serif"><br></font></div><div><font face="arial, sans-serif">Matt</font></div>
<div><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Oct 22, 2013 at 2:46 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"><div class="im">On 23 Oct 2013, at 01:31, Matt Pietrek <<a href="mailto:mpietrek@skytap.com">mpietrek@skytap.com</a>> wrote:<br>
<br>
> Thanks Zhibo. We actually have hundreds of queues. Two of them are processing several hundred messages/second. The remaining queues are processing 1 or 2 messages second.<br>
<br>
</div>Then you should see at least two cores being moderately used.<br>
<br>
As you have correctly identified,<br>
Erlang VM detects 4 cores available to it. What is odd is that you have async-threads:0,<br>
which means disk I/O will block Erlang VM schedulers.<br>
<br>
Does the<br>
<div class="im"><br>
Erlang R15B01 (erts-5.9.1) [source] [64-bit] [smp:4:4] [async-threads:0] [kernel-poll:false]<br>
<br>
</div>line come from RabbitMQ or just `erl` executed on the same machine?<br>
<br>
If you run rabbitmq with RABBITMQ_ALLOW_INPUT=true in the foreground and hit Enter,<br>
you should see how many async-threads it has configured.<br>
For me it's 30 vs 10 for a new Erlang shell.<br>
<br>
I'd also recommend using vmstat and similar tools to see how many threads wait on disk I/O.<br>
By the way, do you publish messages as persistent?<br>
<div class="HOEnZb"><div class="h5"><br>
MK<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>
</div></div></blockquote></div><br></div>