<div dir="ltr">Following up on this, it looks like erlang is seeing all four cores:<div><br></div><div>Erlang R15B01 (erts-5.9.1) [source] [64-bit] [smp:4:4] [async-threads:0] [kernel-poll:false]<br></div><div><br></div><div>
I assume this is what the [smp:4:4] refers to.</div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Oct 22, 2013 at 10:43 AM, Matt Pietrek <span dir="ltr"><<a href="mailto:mpietrek@skytap.com" target="_blank">mpietrek@skytap.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">We're running RabbitMQ 3.0.2 on Ubuntu 10.04 with Erlang 1:15.b.1 on a four CPU box under pretty heavy load.�<div>
<br></div><div>Looking at the per-CPU metrics in VMWare, it looks like the beam.smp process is utilizing only one of the CPUs. One CPU is pegged at near 100%, while the others are nearly idle.</div>
<div><br></div><div>Is there some sort of configuration switch I've overlooked to enable Rabbit/Beam to use all the CPUs?</div><div><br></div><div>Thanks,</div><div><br></div><div>Matt</div></div>
</blockquote></div><br></div>