On Friday, 12 May 2023 11:09:37 BST Arve Barsnes wrote: > On Fri, 12 May 2023 at 10:34, Peter Humphrey <pe...@prh.myzen.co.uk> wrote:
> > I have said several times that portage is ignoring that setting. I have it > > at 40, yet portage kicks off more packages at 72, and continues doing so > > for extended periods - at least 15 minutes. > > But are you sure that it is actually ignored? It was said in an > earlier message from Mark that the value was related to number of > cores, where your 24 cores at 100% average load would translate to a > value of --load-average 24.0. That would put your value of 40 at 166% > average load? What load are you actually trying to limit it to? If you > want 40% load, that should apparently be --load-average 9.6. I'm reading man make.conf, which makes quite clear that --load-average limits the number of portage packages to be emerged, so as to avoid excess load. Simple. Either --load-average is designed to do as the man page says, but it doesn't work and should be fixed, or it should be removed, being useless and misleading. We can't have an option that limits load, but can be ignored at portage's whim. I haven't had a reply to my question in the bug report yesterday: "Why is --load-average=40 being ignored?" but it is perhaps early days yet. A possibility has just occurred to me: it seems to me that the use of a floating-point number for load average is a recent development, at least I've never seen it before and I've always used a plain integer. Could portage be skipping over it when it doesn't find a decimal point? That would be easier to fix than a wholesale failure of function. -- Regards, Peter.
