From 99aac72a16544637e9ab2e14c7b28f64b4638c8e Mon Sep 17 00:00:00 2001 From: Kevin Stock <kevin@kevinstock.org> Date: Wed, 30 Oct 2019 16:53:04 -0400 Subject: [PATCH] docs: fix upper bound on number of consumed cores --- doc/manual/advanced-topics/cores-vs-jobs.xml | 4 ++-- 1 file 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 -- GitLab