Adam Carter wrote: > 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?
A lot of this will obviously depend on CPU speed, number of cores/threads, amount of memory and also, is it compiling on its own or are other packages also being compiled and taking up CPU time or other things using CPU time as well. Here, AMD CPU at 4GHz with 8 cores. 32GBs of memory and most packages built on tmpfs, except large packages. This is a recent few examples. Sat Aug 6 06:34:31 2022 >>> net-libs/webkit-gtk-2.36.5-r1 merge time: 1 hour, 39 minutes and 13 seconds. Sun Aug 21 16:04:23 2022 >>> net-libs/webkit-gtk-2.36.6 merge time: 3 hours, 41 minutes and 44 seconds. Sat Sep 3 22:29:36 2022 >>> net-libs/webkit-gtk-2.36.7 merge time: 2 hours, 41 minutes and 7 seconds. I left out binary emerges and such. Oldest at top, newest at bottom. I suspect for the middle and most likely the bottom one, there was another package compiling as well. It's possible the top one was either on its own part or all of the time. It's really hard to compare these things. Even if our rigs are close in speed/power/whatever, there can still be a lot of things that affect the compile time. I run KDE, watch TV from computer, have torrent software that runs basically 24/7 plus other stuff running. If you for example use Fluxbox and have little else running, even with the same CPU and memory, compile times will vary. Does that info help? Dale :-) :-)
