On Sat, May 06, 2023 at 12:50:08PM +0100, Peter Humphrey wrote > Second, the two pages contribute actively to the confusion between the emerge > jobs submitted in parallel by portage and the concurrent tasks that may be > launched by each of those. > > The test: > > I ran 'emerge -e @world' with EMERGE_DEFAULT_OPTS="--jobs=10 --load- > average=40 ...". It took 350m46s. > > Then I ran the same -e with --load-average=40, but no --jobs and no -j. That > took 351m21s - 35 seconds longer! What's worse, the load average was > controlled at about 72, not 40. I watched it for some time, and even though > all three load averages were at 72-75, portage kept on starting more packages. > > As far as I could see, swap was not touched. > > The machine has 24 threads and 64GB RAM (not to mention plenty of swap), so > how was the 72 figure arrived at?
I think you're over-complicating things here. Forget --jobs and --load-average and their interactions. First of all the Gentoo install handbook has a dire warning that each *THREAD* requires *AT LEAST* 2 GiB of ram. https://wiki.gentoo.org/wiki/Handbook:AMD64/Full/Installation#MAKEOPTS You've got 24 threads and 64 GB RAM, so try... MAKEOPTS="-j20" ...to leave a few threads for your system if your'e playing freecell or whatever. How fast do the builds go? Don't sweat +/- 30 seconds. -- I've seen things, you people wouldn't believe; Gopher, Netscape with frames, the first Browser Wars. Searching for pages with AltaVista, pop-up windows self-replicating, trying to uninstall RealPlayer. All those moments, will be lost in time like tears in rain... time to die.
