From 01ece824e1ddda561acb5f611dc55a1f906e99a3 Mon Sep 17 00:00:00 2001 From: Massimiliano Culpo Date: Tue, 28 May 2019 15:42:04 +0200 Subject: Cap the maximum number of build jobs (#11373) * config:build_jobs now controls the number of parallel jobs to spawn during builds, but cannot ever exceed the number of cores on the machine. * The default is set to 16 or the number of available cores, whatever is lowest. * Updated docs to reflect the changes done to limit parallel builds --- etc/spack/defaults/config.yaml | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) (limited to 'etc') diff --git a/etc/spack/defaults/config.yaml b/etc/spack/defaults/config.yaml index 6e8c1905e8..37db99f4c9 100644 --- a/etc/spack/defaults/config.yaml +++ b/etc/spack/defaults/config.yaml @@ -99,10 +99,12 @@ config: locks: true - # The default number of jobs to use when running `make` in parallel. - # If set to 4, for example, `spack install` will run `make -j4`. - # If not set, all available cores are used by default. - # build_jobs: 4 + # The maximum number of jobs to use when running `make` in parallel, + # always limited by the number of cores available. For instance: + # - If set to 16 on a 4 cores machine `spack install` will run `make -j4` + # - If set to 16 on a 18 cores machine `spack install` will run `make -j16` + # If not set, Spack will use all available cores up to 16. + # build_jobs: 16 # If set to true, Spack will use ccache to cache C compiles. -- cgit v1.2.3-60-g2f50