aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorEelco Dolstra <edolstra@gmail.com>2019-11-05 11:17:02 +0100
committerGitHub <noreply@github.com>2019-11-05 11:17:02 +0100
commit78b8203e500f9ac49b913f303e5e0155d2297c69 (patch)
tree189b03feeb69a0d63b4d3dc193f5aa0c583671c7
parent376802c9b855b9d28ac634dd72b50ea5317d22fd (diff)
parent99aac72a16544637e9ab2e14c7b28f64b4638c8e (diff)
Merge pull request #3180 from kevinastock/patch-1
docs: fix upper bound on number of consumed cores
-rw-r--r--doc/manual/advanced-topics/cores-vs-jobs.xml4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/manual/advanced-topics/cores-vs-jobs.xml b/doc/manual/advanced-topics/cores-vs-jobs.xml
index eba645faf..4d58ac7c5 100644
--- a/doc/manual/advanced-topics/cores-vs-jobs.xml
+++ b/doc/manual/advanced-topics/cores-vs-jobs.xml
@@ -36,8 +36,8 @@ to <xref linkend="conf-cores" />, unless <xref linkend="conf-cores" />
equals <literal>0</literal>, in which case <envar>NIX_BUILD_CORES</envar>
will be the total number of cores in the system.</para>
-<para>The total number of consumed cores is a simple multiplication,
-<xref linkend="conf-cores" /> * <envar>NIX_BUILD_CORES</envar>.</para>
+<para>The maximum number of consumed cores is a simple multiplication,
+<xref linkend="conf-max-jobs" /> * <envar>NIX_BUILD_CORES</envar>.</para>
<para>The balance on how to set these two independent variables depends
upon each builder's workload and hardware. Here are a few example