Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!husc6!husc7!hadeishi
From: hadeishi@husc7.UUCP
Newsgroups: comp.sys.amiga
Subject: Re: Ram: problem with 1.2
Message-ID: <1539@husc6.UUCP>
Date: Tue, 31-Mar-87 13:26:52 EST
Article-I.D.: husc6.1539
Posted: Tue Mar 31 13:26:52 1987
Date-Received: Thu, 2-Apr-87 07:28:55 EST
References: <1332@rutgers.RUTGERS.EDU>
Sender: news@husc6.UUCP
Reply-To: hadeishi@husc7.UUCP (Mitsuharu Hadeishi)
Organization: Harvard Univ. Science Center
Lines: 24
Summary: RAM: has several problems

Re: 1.2 RAM: device . . .

	The RAM: device under 1.2 has several problems, although not
quite as bad as under 1.1.  Sometimes renaming files under the RAM: device
doesn't work correctly.  The absolute WORST problem, though, with the
RAM: device (not even a device, really, just an AmigaDOS Handler), is
that it allocates memory with AllocMem() and thus totally fragments
memory that should be reserved for code and data.  The problem with this
is that if you are using RAM: heavily (for program development, for example),
and thus are writing and deleting small files all the time, you end up with
a free list that looks like Swiss Cheese.  Then, try to edit a document!
With any editor, you end up with you text in a clist which is fragmented
all over memory, so it takes an infinite amount of time just to do a simple
search through a relatively large document (sometimes crashing the machine).
I found the performance of my programs, compilers, and editors improved
500% when I started using Perry's vd0: recoverable RAMdisk device which
does the Right Thing and allocates memory starting from the TOP of RAM
rather than using AllocMem() and allocating from the BOTTOM.

				-Mitsu

P.S.  BTW, Perry, sorry I haven't sent in the $10 yet, but with midterms
and all, well, excuses, excuses.  Okay, I'm writing the check NOW.
Okay, okay, my conscience is finally assuaged!  AAaaaaaah!!!!!!!!