On 2023-02-18, Stefan Schmiedl <s...@xss.de> wrote: > Samstag, 18. Februar 2023 01:49: > >> I have three systems (all ~arch) and the emerge times have blown out on all >> of them across all packages. Worst example appears to be; > >> Fri Dec 23 13:11:44 2022 >>> net-libs/webkit-gtk-2.38.3-r410 >> merge time: 37 minutes and 8 seconds. > >> Fri Dec 23 13:43:08 2022 >>> net-libs/webkit-gtk-2.38.3 >> merge time: 31 minutes and 24 seconds. > >> Sat Feb 4 21:16:40 2023 >>> net-libs/webkit-gtk-2.38.4-r410 >> merge time: 6 hours, 53 minutes and 28 seconds. > >> Sun Feb 5 04:17:12 2023 >>> net-libs/webkit-gtk-2.38.4 >> merge time: 7 hours and 32 seconds. > >> Is anyone else seeing this? > > When I had something like this about two years ago, the culprit was me > setting the cpufreq thingie in the kernel config to powersave or whatever > it's called ... running emerge with 800 MHz instead of 3.2 GHz produced > effects similar to yours.
The same thing happened to me recently. Somehow, I broke the load/temp based CPU clock scaling on one of my machines, and it suddenly took 4X as long to build things as my other machines. It was running at the lowest clock speed possible all the time. Unfortunately, I don't remember exactly what I did to fix it... -- Grant
