Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!sri-unix!ctnews!pyramid!hplabs!nsc!voder!apple!lsr
From: lsr@apple.UUCP (Larry Rosenstein)
Newsgroups: comp.sys.mac
Subject: Re: Possible LSC improvements
Message-ID: <6477@apple.UUCP>
Date: Wed, 14-Oct-87 21:21:48 EDT
Article-I.D.: apple.6477
Posted: Wed Oct 14 21:21:48 1987
Date-Received: Sat, 17-Oct-87 03:03:02 EDT
References: <2071@sfsup.UUCP| <170026@acf3.NYU.EDU>
Reply-To: lsr@apple.UUCP (Larry Rosenstein)
Organization: Advanced Technology Group, Apple Computer
Lines: 29

In article <2638@batcomputer.tn.cornell.edu> eacj@tcgould.tn.cornell.edu (Julian Vrieslander) writes:
>
>This certainly does give a nice speed increase, especially if you have
>2 Meg or more to run around in.  But I am hesitant to use RAM cache when
>I am debugging tricky code that is crashing a lot; I worry about losing
>source changes that have not been written from the cache out to disk.  

You should consult Tech Note #81 on caching.  There is a way to disable
caching if an application needs to do so.

Also, the cache is flushed out when you call FlushVol.  Application should
*ALWAYS* call FlushVol when they finish writing out a file.  If you turn off
the cache in the Control Panel, the system still caches some directory
information, which would not be written out until FlushVol was called.
(This has always been true on the Macintosh, even for MFS volumes.)

I always run with the disk cache on, and haven't lost anything except when I
have failed to save a file.


-- 
Larry Rosenstein

Object Specialist
Apple Computer

AppleLink: Rosenstein1
UUCP:  {sun, voder, nsc, mtxinu, dual}!apple!lsr
CSNET: lsr@Apple.com