Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uwm.edu!zaphod.mps.ohio-state.edu!brutus.cs.uiuc.edu!apple!sun-barr!decwrl!ucbvax!pro-sol.cts.com!ruzun
From: ruzun@pro-sol.cts.com (Roger Uzun)
Newsgroups: comp.sys.apple
Subject: Re: ROM 04 GS and resolution
Message-ID: <17002.apple.net@pro-sol>
Date: 18 Feb 90 20:37:28 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 12

In-Reply-To: message from c60a-3hu@e260-1g.berkeley.edu

Interesting, looks like I way overestimated the relative performance of
a 65816 vs a 68030.  The Apple IIGS w/transwarp gets 274 drystones/sec
My 28 Mhz 68030 w/ BURST and CACHE enabled, and an optimizing C compiler
gets 12,500 drystones/sec/  ALso looks like 100 iterations of sieve,
which take 2 seconds on my 28 Mhz 030 system, take 56 to 90 seconds
on a //gs depending on compiler.
 
Apple really needs to do something about the //gs performance under C.

-R@oger