1 |
On 14/7/20 9:34 am, Sam Jorna (wraeth) wrote: |
2 |
> On 14/7/20 2:33 am, Neil Bothwick wrote: |
3 |
>> You have to consider the --jobs option passed to emerge at the same time. |
4 |
>> It's no use limiting each emerge to 2 processes if you then run multiple |
5 |
>> emerges in parallel. Setting --load in MAKEOPTS and --load-average in |
6 |
>> EMERGE_DEFAULT_OPTS is worthwhile on a constrained system. |
7 |
> |
8 |
> It's also worth pointing out that emerge's --load-average is only |
9 |
> evaluated when it's looking to start building a new package/job, as |
10 |
> opposed to MAKEOPTS' (ie. make's) --load which is evaluated every time |
11 |
> make wants to spawn a new thread. If your load average drops below the |
12 |
> threshold, emerge will start a new job with potentially -jN make threads |
13 |
> (though this is mitigated somewhat if also using --load in MAKEOPTS). |
14 |
|
15 |
Re-sending with (what should now be the) correct GPG signature. |
16 |
|
17 |
Sorry, new mail client, and it's trying to be "helpful". |
18 |
|
19 |
-- |
20 |
Sam Jorna (wraeth) |