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