Path: utzoo!attcan!uunet!cbmvax!jesup
From: jesup@cbmvax.commodore.com (Randell Jesup)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Dhrystone & Diskperf results(?)
Keywords: A3000 dhrystone & diskperf
Message-ID: <13374@cbmvax.commodore.com>
Date: 23 Jul 90 20:12:44 GMT
References: <25660@mimsy.umd.edu>
Reply-To: jesup@cbmvax (Randell Jesup)
Organization: Commodore, West Chester, PA
Lines: 21

In article <25660@mimsy.umd.edu> kelso@mimsy.umd.edu (Stephen Kelley) writes:
>Diskperf:
>	now *this* was more disconcerting...
>	I got 26000 bytes/sec read, 19000bytes/sec write @ 512
>		 200000 bytes/sec read @ 8192
>		 580000 bytes/sec read @ 512K
>	What happened here??? Subjectively, my system *seems* fast.

	Diskperf is pretty brain-dead, which is why there are so many variants
of it around.  DiskSpeed is more reliable as an indicator of true speed, though
the Seek/Read test is a bit over-simplistic.

	That drive you have will probably top 700 or 800 K/s reads on large
reads, as opposed to the 580 number from diskperf.  Diskperf is also
particularily inaccurate at high speeds (one of the reasons DiskSpeed has
three different intensity levels).

-- 
Randell Jesup, Keeper of AmigaDos, Commodore Engineering.
{uunet|rutgers}!cbmvax!jesup, jesup@cbmvax.cbm.commodore.com  BIX: rjesup  
Common phrase heard at Amiga Devcon '89: "It's in there!"