Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!columbia!rutgers!clyde!cbatt!ihnp4!inuxc!pur-ee!uiucdcs!uiucuxc!hamilton
From: hamilton@uiucuxc.CSO.UIUC.EDU
Newsgroups: net.micro.amiga
Subject: Re: aMEGA 1Meg RAM speedup
Message-ID: <148600182@uiucuxc>
Date: Thu, 30-Oct-86 14:06:00 EST
Article-I.D.: uiucuxc.148600182
Posted: Thu Oct 30 14:06:00 1986
Date-Received: Mon, 3-Nov-86 19:49:20 EST
References: <318@pttesac.UUCP>
Lines: 27
Nf-ID: #R:pttesac.UUCP:318:uiucuxc:148600182:000:1167
Nf-From: uiucuxc.CSO.UIUC.EDU!hamilton    Oct 30 13:06:00 1986


vanam@pttesac says:
> I've had one of the CardCo (now called C Ltd) 1 Megabyte memory
> boards for about 3 months now.  It's called the aMEGA RAM board.
> 
> There was some talk in this newsgroup about that board having
> a problem.  It apparently would cause wait states.  I tested it
> with Perry's memtest program and found that the FAST external
> memory (the aMEGA board) was running 27% slower than my CHIP
> internal memory.
> 
> ...
> 
> After the fix I ran Perry's memtest program again.  To my surprise,
> not only did my FAST external memory speed up, but so did my CHIP
> memory!  My CHIP memory sped up by 15%, the FAST memory by 27%.
> I hadn't done the memtest program with my aMEGA board disconnected
> before, but apparently it had caused a slow down in my internal
> memory (besides taking wait states on it's own).  I'm hoping someone
> out there will explain why.

    when you first ran perry's memtest, with the aMEGA connected,
the program's code loaded into FAST mem, didn't it?  so even while
it was flogging data bytes in CHIP mem, the opcodes to do so were
fetched from aMEGA ram.  speedup aMEGA and those instructions fetch
faster.
	wayne