Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!know!sdd.hp.com!ucsd!dog.ee.lbl.gov!pasteur!cory.Berkeley.EDU!navas
From: navas@cory.Berkeley.EDU (David C. Navas)
Newsgroups: comp.sys.amiga
Subject: Re: Benchmark:A3000 w/ AMAXII
Message-ID: <28676@pasteur.Berkeley.EDU>
Date: 10 Oct 90 22:32:03 GMT
References: <1990Oct9.184447.4539@ee.rochester.edu> <15009@cbmvax.commodore.com>
Sender: news@pasteur.Berkeley.EDU
Reply-To: navas@cory.Berkeley.EDU
Lines: 26



In article <15009@cbmvax.commodore.com> daveh@cbmvax.commodore.com (Dave Haynie) writes:
>In article <1990Oct9.184447.4539@ee.rochester.edu> tombs@ee.rochester.edu writes:
>>	A3000/25/50		MacIIci		MacIIcx			MAC+
>>Dhrys/sec 2871(2717)			3736(3816)	(768.8)
 
>The Dhrystone test doesn't use any floating point.  But the results do say
>a few things.  First, that AMAX seems to be taking on a bit more overhead
>than I would have expected.

Hmmm...  Sure that this test was running in FAST and not CHIP memory?  That
might just account for a few differences. You'll need something to soak
up 1 to 2 megs BEFORE you try running the Dhrystone benchmark...

>Secondly, that the compiler used here was lousy;
>typical A3000 Dhrystone 2.1 numbers are in the 5000-8000 range, depending on
>C compiler and settings.

Yep, that's true -- these are the worst figures I've seen since, well since
a long time ago...
Even for the Mac Plus, that's not too good.
 

David Navas                                   navas@sim.berkeley.edu
"Excuse my ignorance, but I've been run over by my train of thought."  -me