Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!mms
From: mms@utgpu.UUCP
Newsgroups: comp.sys.mac
Subject: Re: Possible LSC improvements
Message-ID: <1987Oct14.001232.16873@gpu.utcs.toronto.edu>
Date: Wed, 31-Dec-69 18:59:59 EDT
Article-I.D.: gpu.1987Oct14.001232.16873
Posted: Wed Dec 31 18:59:59 1969
Date-Received: Thu, 15-Oct-87 04:57:24 EDT
References: <2071@sfsup.UUCP| <170026@acf3.NYU.EDU> <2936@husc6.UUCP> <1987Oct9.001743.14846@gpu.utcs.toronto.edu> <21246@ucbvax.BERKELEY.EDU>
Reply-To: mms@gpu.utcs.UUCP (John J. Chew III)
Organization: The Poslfit Committee
Lines: 19
Checksum: 26307

In article <21246@ucbvax.BERKELEY.EDU> oster@dewey.soe.berkeley.edu.UUCP (David Phillip Oster) writes:
> In article <1987Oct9.001743.14846@gpu.utcs.toronto.edu> mms@gpu.utcs.UUCP (John J. Chew III) writes:
> >I'd like to be able to put my header files on a small ramdisk, as reading
> >them in seems to be the most time-consuming part of my compiles
> 
> Why bother? Just crank up the RAM Cache on the control panel and you get
> better than the same effect: the include files that are getting used a lot
> right now, stay in the cache, and you don't have to worry about explicitly
> moving files around.

It's no trouble to move the files, since I can tell the ram disk
program to do that automatically, and if I run LSC with a reasonable
amount of space under switcher there doesn't seem to be enough memory
left over to make the cache effective.
-- 
john j. chew (v3.0)                       poslfit@gpu.utcs.toronto.edu
+1 416 463 5403 (300/1200 bps)            poslfit@utorgpu.bitnet
{cbosgd,decvax,mnetor,utai,utcsri,{allegra,linus}!utzoo}!utgpu!poslfit
"Script-G for open, sub-delta for durchschnitt"