home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.msdos.programmer
- Path: sparky!uunet!charon.amdahl.com!pacbell.com!ames!sun-barr!cs.utexas.edu!zaphod.mps.ohio-state.edu!moe.ksu.ksu.edu!hobbes.physics.uiowa.edu!ack
- From: ack@space.physics.uiowa.edu (Allen Kistler)
- Subject: Re: Ramdrive vs disk cache for temporary files
- Message-ID: <Bxot5q.A5z@space.physics.uiowa.edu>
- Organization: The University of Iowa, Department of Physics and Astronomy
- References: <1992Nov13.180117.20097@tamsun.tamu.edu>
- Distribution: na
- Date: Sat, 14 Nov 1992 03:46:36 GMT
- Lines: 19
-
- In article <1992Nov13.180117.20097@tamsun.tamu.edu>
- tpradeep@cs.tamu.edu (Pradeep K Tapadiya) writes:
- >
- >Some compilers, linkers, and editors create intermediate files
- >which gets deleted at the end of the job.
- >
- >Of a ramdrive or a disk cache, which one is more suitable for
- >such temporary files?
-
- Ramdrive. Sure, with the right disk, the cache will be just as fast, but
- if you do a lot of compiling (or whatever creates temp files) many temp files
- created many times could end up fragmenting your disk.
-
- >How about caching a ram-drive? Does it make sense?
-
- I'd say it's about as sensible as using virtual memory to cache a real disk.
-
- Allen Kistler
- ack@space.physics.uiowa.edu
-