[rabbitmq-discuss] Determining Cause of Flow-Control Invocation

[Michael Klishin]

On oct 4, 2013, at 9:58 p.m., Richard Raseley <richard at raseley.com> wrote:

> Will you expand more on your statement "[I]t's a little more complicated than '1 queue per core'."?

You get one Erlang process per queue. Those are scheduled to run in one or more
run queues (VM queues, nothing to do with RabbitMQ queues). Recent Erlang VM
versions detect how many cores are available on start and create a new run queue
per core.

How scheduling is performed (that is, how processes are given time to run
and distributed between run queues) is not so trivial to explain and varies between
SMP and non-SMP systems, see

http://jlouisramblings.blogspot.ru/2013/01/how-erlang-does-scheduling.html

for a fairly concise and approachable overview.

MK



-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 495 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20131004/ea5cb91d/attachment.pgp>