Path: utzoo!attcan!uunet!zaphod.mps.ohio-state.edu!usc!ucla-cs!oahu.cs.ucla.edu!stephen
From: stephen@oahu.cs.ucla.edu (Steve Whitney)
Newsgroups: comp.sys.atari.st.tech
Subject: Re: Quien es mas macho? (HD caching)
Message-ID: <1990Oct31.162831.10747@cs.ucla.edu>
Date: 31 Oct 90 16:28:31 GMT
References: <1990Oct30.220831.17172@math.lsa.umich.edu>
Sender: news@cs.ucla.edu (Mr. News)
Organization: UCLA Computer Science Department
Lines: 33
Nntp-Posting-Host: oahu.cs.ucla.edu

In article <1990Oct30.220831.17172@math.lsa.umich.edu> hyc@math.lsa.umich.edu (Howard Chu) writes:
>
...
>Hm. With sufficient memory and a good cache, isn't the whole idea of a
>RAMdisk pointless?
>
Well, I use one on my four meg STE for all of the obnoxious temporary files
that Mark Wiliams C insists on writing all the time.  The GEMDOS caching
scheme is a write-through cache (which I appreciate whenever I crash my system
testing a program or someone turns my machine off!), but that means that 
You still at least have to write the temporary files out to disk before they
get cached.

In an ideal worls, the compiler would see tht it had enough memory and use it.
No, I take that back.  In an ideal world, we'd have virtual memory so the
compiler could _always_ use RAM...  The OS would decide when it should go to 
disk!

>  -- Howard Chu @ University of Michigan
>
>Mac// - adv., q.v. MacToo, e.g.  McHave a McHappy McDay!
>		McThanks, McYou MacToo!






-- 
Steve Whitney   "It's never _really_ the last minute"       (())_-_(())
UCLA Comp. Sci. Grad. Student                                | (* *) | 
Internet: stephen@cs.ucla.edu              UCLA Bruin-->    {  \_@_/  }
GEnie:    S.WHITNEY                                           `-----'