Dead wrong. At least if you are not compiling with mem=4m. Compiling is highly CPU bound.
Once i measured compiles time on the same box on to different hardisk, a scsi disk and
an ide disk. Compile time were falling in the same __seconds__ (was something like
12 minute (P5 90MHz))
> interested in measuring the raw CPU power, not the speed of the
> SCSI disks.
>
> I'm using the byte bench 2.0 benchmarks with default options, I don't
> touch anything. It was compiled exactly the same on both the ppro/200 and
> the K6.
>
> People might claim dhrystones are "useless", but unfortunately it does
> seem to be a good indicator of speed, despite what people claim.
>
> E.g. we compared a pentium and a powerpc with dhrystones. People claimed
> powerpc should be faster, but no matter what application we ran, it
> wasn't. In fact, each application showed exactly the same speed as
> dhrystone predicted.
>
> So I don't listen to benchmark-critics any more.
>
> -Dan
-- Philippe Strauss <philou@lili.urbanet.ch>Homepage & PGP key: http://lili.urbanet.ch
"I know not with what weapons World War III will be fought, but World War IV will be fought with sticks and stones." -- Albert Einstein
--