> On 5 Jan 2022, at 19:18, Kai Krakow <[email protected]> wrote: > > Am Mi., 5. Jan. 2022 um 19:22 Uhr schrieb Ulrich Mueller <[email protected] > <mailto:[email protected]>>: >> >>>>>>> [...] >> That applies to all parallel builds though, not only to ebuilds >> inheriting check-reqs.eclass. By tweaking MAKEOPTS, we're basically >> telling the user that the --jobs setting in their make.conf is wrong, >> in the first place. > > Well, I'm using a safe combination of jobs and load-average, maybe the > documentation should be tweaked instead. >
I think "safe" is doing some heavy lifting here... > I'm using > [...] > > The "--jobs" parameter is mostly a safe-guard against "make" or > "emerge" overshooting the system resources which would happen if > running unconstrained without "--load-average". The latter parameter > OTOH tunes the parallel building processes automatically to the > available resources. If the system starves of memory, thus starts to > swap, load will increase, and make will reduce the jobs. It works > pretty well. > > I've chosen the emerge loadavg limit slightly higher so a heavy ebuild > won't starve emerge from running configure phases of parallel ebuilds. > ... because it's quite hard for this logic to work correctly enough of the time without jobserver integration (https://bugs.gentoo.org/692576 <https://bugs.gentoo.org/692576>). But indeed, I'd say you're not the target audience for this (but I appreciate the input). Best, sam
signature.asc
Description: Message signed with OpenPGP
