From:	eplmst AT lu DOT erisoft DOT se (Martin Stromberg)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: rhide compile..
Date:	27 Feb 2000 18:01:03 GMT
Organization:	Ericsson Erisoft AB, Sweden
Lines:	33
Message-ID:	<89boov$4v8$1@antares.lu.erisoft.se>
References:	<Pine DOT LNX DOT 4 DOT 10 DOT 10002252023140 DOT 865-100000 AT darkstar DOT grendel DOT net>
NNTP-Posting-Host:	mars.lu.erisoft.se
X-Newsreader:	TIN [version 1.2 PL2]
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

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.

: A command for setting up a 16 mb smartdrive disk cache would be "smartdrv
: 16000 c+" without the quotes. You can just type it into the dos prompt or
: add it into your autoexec.bat file.

: The "c+" bit means enable write caching to your c drive. If you have
: additional hard drives please add there number too, ie if there is a d:
: drive the you would add "c+ d+" to the above command.

: 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).

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.

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!


Right,

							MartinS

- Raw text -