I'm unfamiliar with Erlang's runtime, so please forgive some basic questions. Is Erlang's runtime doing the thread pinning without any input from you? Or are y

I'm unfamiliar with Erlang's runtime, so please forgive some basic questions. Is Erlang's runtime doing the thread pinning without any input from you? Or are you, at the application level, explicitly telling the Erlang runtime how to pin threads? edit: Did some googling, looks like it's the latter: http://erlang.org/doc/man/erl.html#+sbt http://erlang.org/doc/man/erl.html#+sbt. There are a bunch of policy options where the user picks what behavior they think will work best with their application, on the current system. Key to my point, though is: The runtime system will by default not bind schedulers to logical processors. Providing options where users opt-in to such behavior is good. But the Go proposal, as far as I read, was unilaterally proposing that is how the runtime would work, always. That's not good, for the reasons I stated.