This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: gcc 3.1 branch slowdown?
- From: Loren James Rittle <rittle at latour dot rsch dot comm dot mot dot com>
- To: gcc at gcc dot gnu dot org
- Cc: hjl at lucon dot org
- Date: Wed, 24 Jul 2002 00:31:34 -0500 (CDT)
- Subject: Re: gcc 3.1 branch slowdown?
- Reply-to: rittle at labs dot mot dot com
Responding to HJL, I wrote on the public gcc list:
>> For 0709, total CPU time was: ~62 minutes
>> For 0711, total CPU time was: ~63 minutes
>> For 0717, total CPU time was: ~63 minutes
Someone indirectly asked me in private e-mail why those facts matter
at all. Perhaps, they don't (which I why I stated the sole
near-absolute conclusion that could be reached from the posted data
before observing the near-constant CPU time ;-). However, in my
experience, they do matter.
More to the point, I should have added: From another i386 machine
covering those dates with 3.1.1 prerelease, I saw no regression in
total wall update/build/check time (at -j1 on a single CPU with ~512MB
of physical memory which has not used one iota of swap space since
being booted at the end of June):
07/08 posted first final results at 17:54.
07/10 posted first final results at 17:49.
07/12 posted first final results at 17:54.
07/14 posted first final results at 18:04.
07/16 posted first final results at 17:56.
07/18 posted first final results at 18:04.
07/20 posted first final results at 17:49.
07/22 posted first final results at 18:00.
All days above completed the same total work (with the possible
exception of a high-variance wall time to run ``cvs update'' in the
source tree) and started at the same time (13:51). The jobs ran at
``nice -10'' thus all other jobs on the system tended to get CPU
before these jobs. At this point, it is unknown whether any other
real jobs ran those days. It appears to me that the other load was
"light/none".
Regards,
Loren