aboutsummaryrefslogtreecommitdiff
path: root/doc/manual/src/advanced-topics/cores-vs-jobs.md
diff options
context:
space:
mode:
Diffstat (limited to 'doc/manual/src/advanced-topics/cores-vs-jobs.md')
-rw-r--r--doc/manual/src/advanced-topics/cores-vs-jobs.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/manual/src/advanced-topics/cores-vs-jobs.md b/doc/manual/src/advanced-topics/cores-vs-jobs.md
index 4a9058ca1..9e91ab9c7 100644
--- a/doc/manual/src/advanced-topics/cores-vs-jobs.md
+++ b/doc/manual/src/advanced-topics/cores-vs-jobs.md
@@ -4,13 +4,13 @@ Nix has two relevant settings with regards to how your CPU cores will
be utilized: `cores` and `max-jobs`. This chapter will talk about what
they are, how they interact, and their configuration trade-offs.
- - `max-jobs`
+ - `max-jobs`\
Dictates how many separate derivations will be built at the same
time. If you set this to zero, the local machine will do no
builds. Nix will still substitute from binary caches, and build
remotely if remote builders are configured.
- - `cores`
+ - `cores`\
Suggests how many cores each derivation should use. Similar to
`make -j`.