| 1 |
On Mon, 28 Nov 2011 00:56:17 +0700, Pandu Poluan wrote: |
| 2 |
|
| 3 |
> I don't know where the 'blame' lies, but I've found myself |
| 4 |
> standardizing on MAKEOPTS=-j3, and PORTAGE_DEFAULT_OPTS="--jobs |
| 5 |
> --load-average=<1.6*num_of_vCPU>" |
| 6 |
> |
| 7 |
> (Yes, no explicit number of jobs. The newer portages are smart enough to |
| 8 |
> keep starting new jobs until the load number is reached) |
| 9 |
|
| 10 |
The problem I found with that is the ebuilds load the system lightly to |
| 11 |
start with, before they enter the compile phase, to portage starts dozens |
| 12 |
of parallel ebuilds, then the system gets completely bogged down when |
| 13 |
they start compiling. |
| 14 |
|
| 15 |
|
| 16 |
-- |
| 17 |
Neil Bothwick |
| 18 |
|
| 19 |
If Microsoft made cars: |
| 20 |
"The airbag system would ask "are you sure?" before deploying." |
Archives