On Fri, May 12, 2023 at 9:08 AM Jack <[email protected]> wrote: > > > -j 1 > > -j1 --load-average=40 > > -j1 --load-aveeage=40.0 > > -j1 --load-average=4.0 > > -j1 --load-average=0.4 > > -j10 --load-average=0.4 > > > > etc., and see what happens? > --load-average controls whether or not emerge starts another > job/package, so testing by emerging a single package will not actually > test this. That's why I suggested running some application to get the > load up to 10 (arbitrary number) and then emerging a larger number of > small packages. If --load-average is set to anything less than the > actual load, it should only launch one package at a time. Having that > simple example to add to the bug would give the developers an easy way > to test. > > I think the fact that Peter's actual load went over 70 is because each > individual job/package had no limit on the number of parallel compiles > make could kick off. There is likely no bug there. The real problem > (as Peter keeps pointing out) is that with the load that high, emerge > still starts additional jobs.
Jack, I totally agree, as long as nothing is broken, but yeah, the list I provided was more meant to engender ideas for Peter. One interesting point is that the first Gentoo page I found to look at the emerge man page shows LOAD as the value provided to the --load-average option, but nowhere does it specify anything other than it's a floating point value: https://dev.gentoo.org/~zmedico/portage/doc/man/emerge.1.html For clarification reading other sites, my understanding is that a load average value of 1 in the top application is meant to represent 1 CPU core operating at 100%. Assuming that's true, then on Peter's 24 core machine, with LOAD=40, he's telling emerge it's ok to use more cores than his machine has. Is that consistent with your (or others) understanding? I think the mistake is one of those easy to make ones where the human things 40% (hence 40) and the machine things 40% (hence 0.4) Cheers, Mark
