zhangyiss/spack
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Cap the maximum number of build jobs (#11373)

Browse Source 
* 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
This commit is contained in:
Massimiliano Culpo
2019-05-28 15:42:04 +02:00
committed by Todd Gamblin
parent 2a51e07fde
commit 01ece824e1
6 changed files with 55 additions and 20 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
etc/spack/defaults/config.yaml
View File

@@ -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.