Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!ames!ucbcad!ucbvax!sdcsvax!nosc!marlin!aburto
From: aburto@marlin.UUCP
Newsgroups: comp.sys.amiga
Subject: Re: Amiga Dhrystones...
Message-ID: <941@marlin.UUCP>
Date: Tue, 24-Feb-87 12:27:02 EST
Article-I.D.: marlin.941
Posted: Tue Feb 24 12:27:02 1987
Date-Received: Fri, 27-Feb-87 04:47:52 EST
References: <1365@navajo.STANFORD.EDU> <936@marlin.UUCP> <938@marlin.UUCP> <1395@navajo.STANFORD.EDU>
Reply-To: aburto@marlin.nosc.mil.UUCP (Alfred A. Aburto)
Distribution: world
Organization: Naval Ocean Systems Center, San Diego
Lines: 40
Keywords: Lattice C, Dhrystone, Turbo-Amiga, Benchmark

In article <1395@navajo.STANFORD.EDU> ali@navajo.UUCP (Ali Ozer) writes:
>In article <938@marlin.UUCP> Alfred A. Aburto writes:
>>	The Atari 520ST Dhrystone results were interesting to me because
>>they show that the software can really make a huge difference in the 
>>performance of the system.  There is nearly a factor of 2.5 in the 
>>performance of Lattice C V3.03 ( 450 Dhrystones/sec ) as compared to 
>>Megamax C V1.0 ( 1136 Dhrystones/sec ).  
>Thanks for the effort in getting the results on a Turbo. By the way, do you
>have a Manx compiler? If not, I can send you or post the executable (if
>I figure out how...) for the Dhrystone program I used. (It already includes
>the calls to DateStamp(), etc, for timing.) 
>
>Ali

I did get Manx Aztec C V3.30E to run the Dhrystone on the Turbo-Amiga.
Here are the results(16-bit int):

Amiga       ,68000  ,  7.16MHz, 16-bit memory      ,  1006 / 1082
Turbo-Amiga ,68020  ,  7.16MHz, 16-bit memory      ,  1064 / 1151
Turbo-Amiga ,68020  , 14.32MHz, 32-bit memory      ,  2815 / 2978

You know when the Dhrystone Program (I'm not calling it a Benchmark anymore)
finishes with a run it prints out something like the following:
"This Machine Benchmarks at 6000 Dhrystones/second".  Well this is not
accurate.  A more accurate output would be:

"This System Executes 6000 Dhrystones/second"
"CAUTION: This System with a different compiler"
"may produce an entirely different result."  

Well we just shot ourselves in the foot, because the next question that can
be asked is: 'Well then of what use is the Dhrystone?'.  It is useful for
the comparison of software(compiler) performance on the same or very
similar machines as we saw for the Amiga/Lattice C/Manx Aztec C results.
To go further than this and compare one machine or system against another
without accounting in some manner for the variance in software performance
is pretty shaky if not meaningless as some 'soldiers of the benchmark wars'
have pointed out to me.

Al Aburto