1 |
On Thu, Aug 25, 2005 at 11:51:32AM +0000, Fernando Meira wrote: |
2 |
> I have a P4-2.4GHz laptop. |
3 |
> I forgot to say that the estimation time was made by genlop. And was quite |
4 |
> wrong! It took something like 11h to compile 112 packages, (though I've |
5 |
> interrupted while compiling gcc-3.3.6.. so it had to restart it anew). From |
6 |
> this, I don't know if I should trust genlop anymore.. or is there something |
7 |
> to configure so that it is more accurate? |
8 |
> |
9 |
> Just for the record, the migration to gcc-3.4.4 went just fine.. until now |
10 |
> at least. :) |
11 |
|
12 |
hum. Genlop looks at the past emerge times of the packages, calculates |
13 |
an average based on that. |
14 |
|
15 |
The one thing genlop can't do is figure out how long it takes to merge |
16 |
new packages. So it just skips them. That is the only way I see genlop |
17 |
being wrong by so much. (The other possibility is that you were |
18 |
running the box with a high load WHILE compiling, though I guess you |
19 |
won't be complaining if that were the case.) |
20 |
|
21 |
To be honest, I've found the genlop time quite reliable... I've |
22 |
rebuilt my systems with --emptytree a few times in the past 6 months. |
23 |
(Once after killing PAM and LDAP, once after changing to hardened, |
24 |
once after changing from ~x86 to x86, and once after a major rehaul of |
25 |
my USE flags; these are on my desktop machine only). The 500 or so |
26 |
packages came up to be 1 day and 15 hours from genlop. The actual |
27 |
compiles never took more than 2 days, and that was while the computer |
28 |
was still in use. Once it actually finished before the estimated time. |
29 |
|
30 |
Do note that, however, genlop can only calculate its merge time based |
31 |
on past averages. So if you made major changes to your system, or if |
32 |
the codebase changed significantly upstream, genlop can be completely |
33 |
wrong. For example, looking at past emerges of glibc, I see the |
34 |
compile time goes from everything between 28 minutes to 3 hours. |
35 |
genlop tells me that if I were to remerge glibc it would take me 1 |
36 |
hour and 9 minutes. But I know from experience if I were to install |
37 |
2.3.5-r1, it will most likely only take me 40 minutes, and if I were |
38 |
to compile glibc-2.3.4.20050125-r1, it will take me about 2 hour and |
39 |
10 minutes. Why the funky discrepancy I don't know. So I think that |
40 |
while genlop is generally rather reliable for a rough idea on how long |
41 |
I need to wait for the compile (i.e. is it worth it just sitting here |
42 |
reading a book or should I just go to bed), the numbers it give should |
43 |
be taken with a grain of salt if you don't have a large number of |
44 |
history of emerges for it to base its guesses on. |
45 |
|
46 |
W |
47 |
|
48 |
-- |
49 |
"Anyone who is capable of getting themselves made President |
50 |
should on no account be allowed to do the job." |
51 |
|
52 |
- Some wisdom from The Book. |
53 |
Sortir en Pantoufles: up 13 days, 18:42 |
54 |
-- |
55 |
gentoo-user@g.o mailing list |