Maximum Processes | -Result | -|||
---|---|---|---|---|
1 | -24 | -24 | -24 | -- One derivation will be built at a time, each one can use 24 - cores. Undersold if a job can’t use 24 cores. - | -
4 | -6 | -6 | -24 | -- Four derivations will be built at once, each given access to - six cores. - | -
12 | -6 | -6 | -72 | -- 12 derivations will be built at once, each given access to six - cores. This configuration is over-sold. If all 12 derivations - being built simultaneously try to use all six cores, the - machine's performance will be degraded due to extensive context - switching between the 12 builds. - | -
24 | -1 | -1 | -24 | -- 24 derivations can build at the same time, each using a single - core. Never oversold, but derivations which require many cores - will be very slow to compile. - | -
24 | -0 | -24 | -576 | -- 24 derivations can build at the same time, each using all the - available cores of the machine. Very likely to be oversold, - and very likely to suffer context switches. - | -
plugthe - various packages into each other.
Checking for the - canonical Nix system namein the output of Nix's -
normalvalues that can be passed around and manipulated -in interesting ways. The language is not a full-featured, general -purpose language. Its main job is to describe packages, -compositions of packages, and the variability within -packages.
standardenvironment consisting of the things you - would expect in a basic Unix environment: a C/C++ compiler (GCC, - to be precise), the Bash shell, fundamental Unix tools such as -
human-readablename for - packages. This attribute is required by -
inputs. This means that if a package provides a -
infinite recursion -encountered).
valid. If you try to build the derivation again, Nix -will see that the path is already valid and finish immediately. If a -build fails, either because it returns a non-zero exit code, because -Nix or the builder are killed, or because the machine crashes, then -the output paths will not be registered as valid. If you try to build -the derivation again, Nix will remove the output paths if they exist -(e.g., because the builder died half-way through
negative caching: Nix doesn't remember that a build -failed, and so a failed build can always be repeated. This is because -Nix cannot distinguish between permanent failures (e.g., a compiler -error due to a syntax error in the source) and transient failures -(e.g., a disk full condition).
Hello, world!.