Ricardo Wurmus <rek...@elephly.net> skribis: > Ludovic Courtès <l...@gnu.org> writes: > >> Ricardo Wurmus <rek...@elephly.net> skribis: >> >>> I’ve tried “guix pull” on the same server again, this time limiting CPUs >>> with “taskset -c 0 guix pull”: >> >> As a stopgap, commit aba219af0fed6a349af930f19c913fb87e6a69dd ensures >> that ‘--cores’ is honored. So if you run “guix pull --cores=1”, it will >> build things sequentially. >> >> Now, to take advantage of that, you first need to update to the current >> Guix… > > Thank you, this worked! > > On that server I built Guix from source and then let the users pull with > “--cores=1” to update their own Guix.
You could also run guix-daemon with --cores=4 or similar, so that it uses 4 cores by default (few package builds scale beyond that anyway), and then maybe --max-jobs=4 so you don’t waste the other cores. ;-) Ludo’.
