🚀 go-pugleaf

In article <1992Aug10.152435.10393@svcdudes.com> moose@svcdudes.com writes:
>Maybe this should be a FAQ.  No, it's not a joke.  And yes it's useful.  How  
>about if instead of calling it a Ramdisk we call it a memory lockin program.
>That means that whatever you put on the Ramdisk won't swap out.  I would love 
>to put things like cc and ccp and compiled headers on a Ramdisk to speed up my
>compiles.

There was a post about a year ago from someone at NeXT explaining that they had
written a ramdisk device and set it up as /tmp for big system builds.

If I recall correctly, the end result was that it was pointless.

I also recall Scott Hess posting at one point that he was using the -pipe
option on a machine loaded with memory and he was getting significantly
better build times (no /tmp files are created, all the phases are done in
parallel), Scott?

Instead of wasting time grafting PC/Amiga/Mac tricks onto the NeXT, the
time would be better spent doing things like coming up with an awesome
SCSI device driver than can do synch requests and has transfer speeds worthy
of the machine it runs on.  There have been more than enough posts to 
prove beyond a reasonable doubt that the NeXTs SCSI device driver simply
stinks speedwise. Memory is typically the LAST thing the NeXT has to spare.

la la la,
-- 
:: Christopher Lloyd :: a74k110@titan.ucc.umass.edu :: Yrrid, Inc. ::