<div dir="ltr">Michael,<div><br></div><div>Thank you for that explanation - it was helpful.</div><div><br></div><div>Regards,</div><div><br></div><div>Richard�</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">
On Fri, Oct 4, 2013 at 11:23 AM, Michael Klishin <span dir="ltr"><<a href="mailto:michael@rabbitmq.com" target="_blank">michael@rabbitmq.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"><br>
On oct 4, 2013, at 9:58 p.m., Richard Raseley <<a href="mailto:richard@raseley.com">richard@raseley.com</a>> wrote:<br>
<br>
> Will you expand more on your statement "[I]t's a little more complicated than '1 queue per core'."?<br>
<br>
</div>You get one Erlang process per queue. Those are scheduled to run in one or more<br>
run queues (VM queues, nothing to do with RabbitMQ queues). Recent Erlang VM<br>
versions detect how many cores are available on start and create a new run queue<br>
per core.<br>
<br>
How scheduling is performed (that is, how processes are given time to run<br>
and distributed between run queues) is not so trivial to explain and varies between<br>
SMP and non-SMP systems, see<br>
<br>
<a href="http://jlouisramblings.blogspot.ru/2013/01/how-erlang-does-scheduling.html" target="_blank">http://jlouisramblings.blogspot.ru/2013/01/how-erlang-does-scheduling.html</a><br>
<br>
for a fairly concise and approachable overview.<br>
<span class="HOEnZb"><font color="#888888"><br>
MK<br>
<br>
<br>
<br>
</font></span></blockquote></div><br></div>