diff options
author | Rickard Green <[email protected]> | 2010-06-03 12:43:57 +0000 |
---|---|---|
committer | Erlang/OTP <[email protected]> | 2010-06-03 12:43:57 +0000 |
commit | 97fa9fe68af5990a8ef7a71ccb7fc235d20a2c04 (patch) | |
tree | 8fbbe0bb2d4e1357b5dbf5af7e9efa2c401408d3 /INSTALL-CROSS.md | |
parent | 8335159b919cc330e1c529464b6bbf89edbbe0a0 (diff) | |
download | otp-97fa9fe68af5990a8ef7a71ccb7fc235d20a2c04.tar.gz otp-97fa9fe68af5990a8ef7a71ccb7fc235d20a2c04.tar.bz2 otp-97fa9fe68af5990a8ef7a71ccb7fc235d20a2c04.zip |
OTP-8666 Enable automatic binding of schedulers when possible
The runtime system will by default bind schedulers to logical processors
using the default_bind bind type if the amount of schedulers are at least
equal to the amount of logical processors configured, binding of schedulers
is supported, and a CPU topology is available at startup.
NOTE: If the Erlang runtime system is the only operating system process
that binds threads to logical processors, this improves the performance of
the runtime system. However, if other operating system processes (as for
example another Erlang runtime system) also bind threads to logical
processors, there might be a performance penalty instead. If this is the
case you, are are advised to unbind the schedulers using the <seealso
marker="erl#+sbt">+sbtu</seealso> command line argument, or by invoking
<seealso
marker="erlang#system_flag_scheduler_bind_type">erlang:system_flag(schedule
r_bind_type, unbound)</seealso>.
Diffstat (limited to 'INSTALL-CROSS.md')
0 files changed, 0 insertions, 0 deletions