Samstag, 18. Februar 2023 19:05: > >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. >> >>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... CONFIG_CPU_FREQ_GOV_PERFORMANCE CONFIG_CPU_FREQ_GOV_POWERSAVE CONFIG_CPU_FREQ_GOV_USERSPACE CONFIG_CPU_FREQ_GOV_ONDEMAND CONFIG_CPU_FREQ_GOV_CONSERVATIVE CONFIG_CPU_FREQ_GOV_SCHEDUTIL Back when I finally found it, all of these were set to "n" but for POWERSAVE which was set to "y". I rebuilt the kernel to use ONDEMAND and things were back to normal. s.
