aboutsummaryrefslogtreecommitdiffstats
path: root/erts/doc/src/erlang.xml
diff options
context:
space:
mode:
authorRickard Green <[email protected]>2011-11-30 13:59:14 +0100
committerRickard Green <[email protected]>2011-11-30 13:59:14 +0100
commitc2c93dd69c0d66a836ec938aeabbc7130960e445 (patch)
tree119903c273301f6c2121d010d9b3957d01d70af4 /erts/doc/src/erlang.xml
parent9b4bc065ba9fb47a9573d5e11f306452a65df3f1 (diff)
parent58f5f45566b827e74ff623398bdf6d0b6fcebdb3 (diff)
downloadotp-c2c93dd69c0d66a836ec938aeabbc7130960e445.tar.gz
otp-c2c93dd69c0d66a836ec938aeabbc7130960e445.tar.bz2
otp-c2c93dd69c0d66a836ec938aeabbc7130960e445.zip
Merge branch 'rickard/default-unbound/OTP-9726'
* rickard/default-unbound/OTP-9726: Use unbound schedulers as default
Diffstat (limited to 'erts/doc/src/erlang.xml')
-rw-r--r--erts/doc/src/erlang.xml14
1 files changed, 5 insertions, 9 deletions
diff --git a/erts/doc/src/erlang.xml b/erts/doc/src/erlang.xml
index 2ea144eb3f..d685728862 100644
--- a/erts/doc/src/erlang.xml
+++ b/erts/doc/src/erlang.xml
@@ -5200,21 +5200,17 @@ true</pre>
For more information on how to define the CPU topology, see
<seealso marker="#system_flag_cpu_topology">erlang:system_flag(cpu_topology, CpuTopology)</seealso>.
</p>
- <p>The runtime system will by default bind schedulers to logical
- processors using the <c>default_bind</c> 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.
+ <p>The runtime system will by default <em>not</em> bind schedulers
+ to logical processors.
</p>
<p><em>NOTE:</em> 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 <c>erlang:system_flag(scheduler_bind_type, unbound)</c>.</p>
+ might be a performance penalty instead. In some cases this
+ performance penalty might be severe. If this is the case, you
+ are advised to not bind the schedulers.</p>
<p>Schedulers can be bound in different ways. The <c>How</c>
argument determines how schedulers are bound. <c>How</c> can
currently be one of:</p>