Ok, I'm not an expert here, but you have several options available to you when determining your scheduler topology. What you'd want to look at if you really wan

Ok, I'm not an expert here, but you have several options available to you when determining your scheduler topology. What you'd want to look at if you really want to make sure to bind your dirty scheduler to a particular core is the +sbt option[1]. However, that's probably not a setting I'd tweak lightly—the OS in general and BEAM in particular is going to do a better job at that than you are under most circumstances. There is definitely a cost to using the dirty scheduler, and if your NIFs don't need it, you're going to be paying the overhead for nothing. But obviously there's a plethora of uses for them when integrating with libraries that don't play nice with chunked work. http://erlang.org/doc/man/erl.html#+sbt http://erlang.org/doc/man/erl.html#+sbt