On Sun, Nov 27, 2011 at 6:21 PM, Neil Bothwick <n...@digimed.co.uk> wrote: > On Mon, 28 Nov 2011 00:56:17 +0700, Pandu Poluan wrote: > >> I don't know where the 'blame' lies, but I've found myself >> standardizing on MAKEOPTS=-j3, and PORTAGE_DEFAULT_OPTS="--jobs >> --load-average=<1.6*num_of_vCPU>" >> >> (Yes, no explicit number of jobs. The newer portages are smart enough to >> keep starting new jobs until the load number is reached) > > The problem I found with that is the ebuilds load the system lightly to > start with, before they enter the compile phase, to portage starts dozens > of parallel ebuilds, then the system gets completely bogged down when > they start compiling.
I did notice that, but it settles back down *very* quickly with the -l parameter to make. -- :wq
