Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!rutgers!mit-eddie!husc6!panda!genrad!decvax!decwrl!labrea!navajo!ali
From: ali@navajo.UUCP
Newsgroups: comp.sys.amiga
Subject: Amiga Dhrystones...
Message-ID: <1365@navajo.STANFORD.EDU>
Date: Thu, 5-Feb-87 17:03:20 EST
Article-I.D.: navajo.1365
Posted: Thu Feb  5 17:03:20 1987
Date-Received: Wed, 11-Feb-87 18:58:48 EST
Reply-To: ali@navajo.ARPA (Ali Ozer)
Distribution: world
Organization: Stanford University
Lines: 57

---

I just downloaded the dhrystone posting from comp.sys.misc and tried it out
on the Amiga. The dhrystone info for the Amiga dated to about a year ago, 
and was for the Manx 2.30a compiler... (Was there ever such a beast? Or does
that mean 3.20a?) Also the OS was probably 1.1, and I was curious what
values I would get with Manx 3.30e and 1.2 OS. 

Here is the old info:
                                          Dhrystones
System, OS, Compiler                    NoReg / WithReg
------------------------------------------------------------
Amiga 1.1, Manx 2.30a (?), 32-bit ints    643 / 684   
Amiga 1.1, Manx 2.30a (?), 16-bit ints    880 / 915  

Here's what I got:
------------------------------------------------------------
Amiga 1.2, Manx 3.30e, 16-bit ints        888 / 945   Workbench screen up
Amiga 1.2, Manx 3.30e, 16-bit ints        906 / 964   Workbench screen down

I did two tests above, and in one I pulled the WB screen way down (so 
I could only see the drag bar). As you can see, that speeded up things
a tiny bit. Then I experimented with turning multitasking off:

------------------------------------------------------------
Amiga 1.2, Manx 3.30e, 16-bit ints        935 / 996   With Forbid/Permit
Amiga 1.2, Manx 3.30e, 16-bit ints        961 / 1026  With Disable/Enable

In both cases above the screen was pulled down (only 10% visible). Note
that Forbid/Permit simply assure that no other task gets to run, but
multitasking still continues (it is as if my priority is set to the max
and no other task's is). Disable/Enable, on the other hand, simply turn
of all interrupts associated with multitasking. I was first afraid to
try using Disable/Enable, but nothing tragic happened. (Actually, the
click-click from my empty second disk drive stopped for the duration
of the test!). But, some things still go on --- I was using DateStamp()
to get the time, and that still worked fine. (I guess because time is
not kept by interrupts but by the 8250s?)

Anyway, here are some other results from the dhrystone posting. 
---------------------------------------------------------------
Mac 512, DeSmet C                            625 / 625 
Mac 512E, Lightspeed C                       510 / 549
Mac Plus (7.8 MHz), Manx, 16-bit ints        714 / 769
Atari 520ST (8 MHz), Lattice 3.03            446 / 450
Atari 520ST,(8 MHz), Megamax C              1063 / 1136

One final note... I was not able to get results with "fast" memory,
as I am still in the 512K world. (Soon soon to be 2 megs I hope!).
Will the program run faster if in fast memory? 

I sent the above results to the dhrystone people. It would be nice
if someone out there with a Turbo Amiga (like the people who did the
Savage floating point stuff?) tried the dhrystones out and also sent in
the results.

Ali Ozer, ali@navajo.stanford.edu