| 1 |
Adam Carter wrote: |
| 2 |
> I have three systems (all ~arch) and the emerge times have blown out |
| 3 |
> on all of them across all packages. Worst example appears to be; |
| 4 |
> |
| 5 |
> Fri Dec 23 13:11:44 2022 >>> net-libs/webkit-gtk-2.38.3-r410 |
| 6 |
> merge time: 37 minutes and 8 seconds. |
| 7 |
> |
| 8 |
> Fri Dec 23 13:43:08 2022 >>> net-libs/webkit-gtk-2.38.3 |
| 9 |
> merge time: 31 minutes and 24 seconds. |
| 10 |
> |
| 11 |
> Sat Feb 4 21:16:40 2023 >>> net-libs/webkit-gtk-2.38.4-r410 |
| 12 |
> merge time: 6 hours, 53 minutes and 28 seconds. |
| 13 |
> |
| 14 |
> Sun Feb 5 04:17:12 2023 >>> net-libs/webkit-gtk-2.38.4 |
| 15 |
> merge time: 7 hours and 32 seconds. |
| 16 |
> |
| 17 |
> Is anyone else seeing this? |
| 18 |
|
| 19 |
|
| 20 |
A lot of this will obviously depend on CPU speed, number of |
| 21 |
cores/threads, amount of memory and also, is it compiling on its own or |
| 22 |
are other packages also being compiled and taking up CPU time or other |
| 23 |
things using CPU time as well. Here, AMD CPU at 4GHz with 8 cores. |
| 24 |
32GBs of memory and most packages built on tmpfs, except large |
| 25 |
packages. This is a recent few examples. |
| 26 |
|
| 27 |
|
| 28 |
Sat Aug 6 06:34:31 2022 >>> net-libs/webkit-gtk-2.36.5-r1 |
| 29 |
merge time: 1 hour, 39 minutes and 13 seconds. |
| 30 |
|
| 31 |
Sun Aug 21 16:04:23 2022 >>> net-libs/webkit-gtk-2.36.6 |
| 32 |
merge time: 3 hours, 41 minutes and 44 seconds. |
| 33 |
|
| 34 |
Sat Sep 3 22:29:36 2022 >>> net-libs/webkit-gtk-2.36.7 |
| 35 |
merge time: 2 hours, 41 minutes and 7 seconds. |
| 36 |
|
| 37 |
|
| 38 |
|
| 39 |
I left out binary emerges and such. Oldest at top, newest at bottom. I |
| 40 |
suspect for the middle and most likely the bottom one, there was another |
| 41 |
package compiling as well. It's possible the top one was either on its |
| 42 |
own part or all of the time. |
| 43 |
|
| 44 |
It's really hard to compare these things. Even if our rigs are close in |
| 45 |
speed/power/whatever, there can still be a lot of things that affect the |
| 46 |
compile time. I run KDE, watch TV from computer, have torrent software |
| 47 |
that runs basically 24/7 plus other stuff running. If you for example |
| 48 |
use Fluxbox and have little else running, even with the same CPU and |
| 49 |
memory, compile times will vary. |
| 50 |
|
| 51 |
Does that info help? |
| 52 |
|
| 53 |
Dale |
| 54 |
|
| 55 |
:-) :-) |
Archives