🚀 go-pugleaf

In article <15987@cbmvax.commodore.com> jesup@cbmvax.commodore.com (Randell Jesup) writes:
>In article <5748@crash.cts.com> lkoop@pnet01.cts.com (Lamonte Koop) writes:
>>(click a test gadget and go).  The problem is this: Running the tests under
>>AmigaOS 1.3 is just fine...results come up generally as expected.  AmigaOS 2.0
>>is a completely different story.  The tests are running _slower_!  And not
>>just a bit slower, but a great deal so.  At first, I thought it was a strange
>
>	There are a number of possibilities.  First, background processes (such
>as commodities like screenblankers) may be eating some CPU time.  Second, some
>calls might not be quite as fast due to relaxing certain limits on them (like
>the longest line that can be drawn: was ~1024, now it's much larger).
>
>	A good way to remove most extraneous variables is to turn off the
>startup-sequence (hold both mouse buttons down, and disable it when the
>BootMenu comes up).  Then run your benchmark.
>
	I ran dhrystones using Forbid(), so other tasks should be
irrelevant. On my 3000 I got a difference of 120 dhrystones/sec
between 1.3 and 2.0.

>-- 
>Randell Jesup, Keeper of AmigaDos, Commodore Engineering.
>{uunet|rutgers}!cbmvax!jesup, jesup@cbmvax.commodore.com  BIX: rjesup  
>Thus spake the Master Ninjei: "If your application does not run correctly,
>do not blame the operating system."  (From "The Zen of Programming")  ;-)


	-- Ethan

	Woody Allen on Los Angeles:

	"I mean, who would want to live in a place where the only
cultural advantage is that you can turn right on a red light?"