Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!elroy.jpl.nasa.gov!sdd.hp.com!samsung!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!tut.cis.ohio-state.edu!ucunix.san.uc.edu!zuazaga
From: zuazaga@ucunix.san.uc.edu (Humberto Oritz-Zuazaga)
Newsgroups: comp.binaries.ibm.pc.d
Subject: Re: What disk caches work with djgcc?
Summary: Use a ramdisk too
Keywords: djgpp, memory, ramdisk
Message-ID: <1991May16.123859.1868@ucunix.san.uc.edu>
Date: 16 May 91 12:38:59 GMT
References: <1991May15.150542.24705@syd.dit.CSIRO.AU>
Organization: Univ. of Cincinnati
Lines: 19

In article <1991May15.150542.24705@syd.dit.CSIRO.AU>
evans@syd.dit.CSIRO.AU (Bruce.Evans) writes:

>only tried smartdrv and hyperdisk). djgcc is very slow without
>extended memory (it swaps all the time) and fairly slow without
>a cache in 7MB extended memory (it accesses the disk a lot).

Try setting TMP as a ramdisk.  With 7megs of memory, you should have
room to spare.  Failing that, I'd try putting the compiler passes in a
ramdisk (the passes are 500k and 700k).  But I'm running on a 20MHz
386SX with 4meg and I don't find it that slow.

P.S.  What am I supposed to do with those long attribution lines, wrap
them or send them out >80 columns?

-- 
Humberto Ortiz-Zuazaga                               University of Cincinnati
                                                      Physiology & Biophysics
zuazaga@ucunix.san.uc.edu                            Cincinnati OH 45267-0576