Date:	Tue, 29 Feb 2000 05:47:00 +0600 (LKT)
From:	Kalum Somaratna aka Grendel <kalum AT crosswinds DOT net>
X-Sender:	root AT darkstar DOT grendel DOT net
To:	djgpp AT delorie DOT com
Subject:	Re: rhide compile..
In-Reply-To:	<89boov$4v8$1@antares.lu.erisoft.se>
Message-ID:	<Pine.LNX.4.10.10002290538530.1008-100000@darkstar.grendel.net>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
Errors-To:	dj-admin AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On 27 Feb 2000, Martin Stromberg wrote:

> Kalum Somaratna aka Grendel (kalum AT crosswinds DOT net) wrote:
> : I use smartdrive to speed up compiles and IMHO it is better than ramdrive
> : especially when write caching is enabled. Also there is no need to fool
> : around with tmp environment variable etc.
<snip> 
> : Then just relax and see how lightning fast the compiles turn out to be...
> : :-)
> 
> A ramdisk is certainly not a replacement for a disk cache! But GCC and
> friends generate voluminous (temporary) output, so a ramdisk will
> speed up the compiling even more than what a disk cache would be able
> to do (at least the disk caches of *DOZE).

I don't think that this will have anydifference because if you have a
samrtdrv (disk cache) with write caching (delayed writing) enabled, the
disk writes should be as low as possible (maybe even no disk writes as all
the temp files as deleted in the end!)

So a diskcache with write caching would be more easier and more effective
than a ramdrive.

> 
> Futhermore as pipes are implemented as temporary files on *DOZE (at
> least for DOZE programs) this will speed up all commands using pipes
> as well.

My above message comments on this.

> 
> For _really_ lightning compiles, make a 64MiB ramdisk (or bigger if
> you have the RAM) and put the whole toolchain and your sources on
> it. And watch the speed!

My point is that you *dont* have to go to this much trouble installing
ramdisk's, setting temp variables etc.

Using your example if you can allocate 64mb just allocate a 64mb! smartdrv
with write caching enabled and after the first compile all the other
compiles will almost certainly be ligtning fast, since after the first
compile the disk cache would have cached all the gcc.exe and librarys etc.
And there will be more efficient memory usage as there is no need to
allocate memory as in a ramdisk for the whole tool chain, for how many of
the tools do we actually use?

Grendel

Hi, I'm a signature virus. plz set me as your signature and help me spread
:)

- Raw text -