Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!maverick.ksu.ksu.edu!maverick.ksu.ksu.edu!brtmac From: brtmac@maverick.ksu.ksu.edu (Brett McCoy) Newsgroups: comp.unix.internals Subject: Re: RAM disk. Message-ID: <1990Oct10.021856.14896@maverick.ksu.ksu.edu> Date: 10 Oct 90 02:18:56 GMT References: <18560@rpp386.cactus.org> <143359@sun.Eng.Sun.COM> <18574@rpp386.cactus.org> <1850@necisa.ho.necisa.oz> <1990Oct09.121447.3336@virtech.uucp> Sender: news@maverick.ksu.ksu.edu (The News Guru) Organization: Kansas State University Lines: 18 In kessler@hacketorium.Eng.Sun.COM (Tom Kessler) writes: >Maybe you could tweak the file system to "know this" but for whatever >I've found tmpfs to speed up compiles quite a bit. Has anyone done any comparisons between compiling using a RAM tmp disk and using the -pipe option on the compiler. Seems to me that they would be much the same since both use memory only and not a lot of temporary files on a physical disk, they just go about it differently. I'm still running 4.0.3c so I can't really try this out. -- Too bad the universe doesn't run in a segmented environment with protected memory. -- Wiz from "Wizards Bane" by Rick Cook Brett McCoy | Kansas State University brtmac@maverick.ksu.ksu.edu | UseNet news manager.