On Saturday, 6 May 2023 19:18:25 BST Jack wrote: > Minor point - are you sure ccache isn't affecting your results?
Pretty sure - it isn't installed here. :) > I hope I'm not preaching to the choir, and I have NOT reread the > various man pages, but the different options you mention (and some you > don't) apply to different parts of the process. Some tell emerge > whether or not to start working on another package, but once it starts > the process, it has no control over how busy the machine can get. Then > there are those that get passed to make. I wouldn't think so, but are > you possibly confusing the two? Lastly, I don't see that those that > apply to make would have any effect on packages that use ninja instead, > so that might also contribute to the issue.. Yes, I understand all that; it all points to the confusion encouraged by the man pages. > Separate question, only vaguely related: is there any easy way to tell > what build tools (ninja vs make, gcc vs clang vs ?) were used for an > installed package without actually looking into the ebuild? It's > probably not relevant to your question about controlling the load, but > I used to rebuild everything after installing a new version of gcc, and > have since realized there are many packages that make no use of gcc, so > the rebuild serves no point, and I miss rebuilding packages that use > clang after an upgrade of it and related tools. Good questions, but I don't think they're related to mine. I just want to know how to control the number of simultaneous tasks during a big emerge - or any emerge, really. -- Regards, Peter.
