From:	Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: slow operation
Date:	3 Aug 2003 22:52:07 GMT
Organization:	Aachen University of Technology (RWTH)
Lines:	26
Message-ID:	<bgk3mn$emn$1@nets3.rz.RWTH-Aachen.DE>
References:	<3f2cff90$1 AT news DOT bezeqint DOT net> <3f2d01d3$0$165$cc7c7865 AT news DOT luth DOT se> <3f2d82c1 AT news DOT bezeqint DOT net>
NNTP-Posting-Host:	acp3bf.physik.rwth-aachen.de
X-Trace:	nets3.rz.RWTH-Aachen.DE 1059951127 15063 137.226.32.75 (3 Aug 2003 22:52:07 GMT)
X-Complaints-To:	abuse AT rwth-aachen DOT de
NNTP-Posting-Date:	3 Aug 2003 22:52:07 GMT
Originator:	broeker@
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Klayhamn <psycho AT isdn DOT net DOT il> wrote:


> I did as 3.9 instructed, and 7.1 didn't really do any good
> it still takes me just as long even with write-back enabled, cpu caching
> (internal and external)
> and a 8MB ramdrive (and yes i set the tmpdir in djgpp.env to point to it)

That may not have taken the desired effect.  You should probably check
where the temp files actually end up (--> the -v option to gcc/gpp)
there.  8 MB may actually be a bit small for C++ source code including
STL headers.  With a properly configured write-back disk cache, a
ramdrive will not typically have much of an effect.

#include <iostream>

is nowhere near as innocent as it may appear.  It expands to 750
kilobytes of preprocessed code, on this Linux box...

And even this 1000 MHz Athlon here takes 1.2 seconds of raw CPU time
to compile hello.cc, so your 5 seconds on a 166 MHz aren't all that
bad at all.

-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.

- Raw text -