| 1 |
On 2023-02-18, Stefan Schmiedl <s@×××.de> wrote: |
| 2 |
> Samstag, 18. Februar 2023 01:49: |
| 3 |
> |
| 4 |
>> 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; |
| 5 |
> |
| 6 |
>> Fri Dec 23 13:11:44 2022 >>> net-libs/webkit-gtk-2.38.3-r410 |
| 7 |
>> merge time: 37 minutes and 8 seconds. |
| 8 |
> |
| 9 |
>> Fri Dec 23 13:43:08 2022 >>> net-libs/webkit-gtk-2.38.3 |
| 10 |
>> merge time: 31 minutes and 24 seconds. |
| 11 |
> |
| 12 |
>> Sat Feb 4 21:16:40 2023 >>> net-libs/webkit-gtk-2.38.4-r410 |
| 13 |
>> merge time: 6 hours, 53 minutes and 28 seconds. |
| 14 |
> |
| 15 |
>> Sun Feb 5 04:17:12 2023 >>> net-libs/webkit-gtk-2.38.4 |
| 16 |
>> merge time: 7 hours and 32 seconds. |
| 17 |
> |
| 18 |
>> Is anyone else seeing this? |
| 19 |
> |
| 20 |
> When I had something like this about two years ago, the culprit was me |
| 21 |
> setting the cpufreq thingie in the kernel config to powersave or whatever |
| 22 |
> it's called ... running emerge with 800 MHz instead of 3.2 GHz produced |
| 23 |
> effects similar to yours. |
| 24 |
|
| 25 |
The same thing happened to me recently. Somehow, I broke the load/temp |
| 26 |
based CPU clock scaling on one of my machines, and it suddenly took 4X |
| 27 |
as long to build things as my other machines. It was running at the |
| 28 |
lowest clock speed possible all the time. Unfortunately, I don't |
| 29 |
remember exactly what I did to fix it... |
| 30 |
|
| 31 |
-- |
| 32 |
Grant |
Archives