Xref: utzoo comp.arch:4193 comp.unix.wizards:7505
Path: utzoo!utgpu!water!watmath!clyde!att-cb!att-ih!alberta!ubc-cs!van-bc!sl
From: sl@van-bc.UUCP (pri=-10 Stuart Lynne)
Newsgroups: comp.arch,comp.unix.wizards
Subject: Re: How fast are your disks?
Keywords: Disk I/O throughput
Message-ID: <1703@van-bc.UUCP>
Date: 2 Apr 88 10:48:03 GMT
References: <3842@watcgl.waterloo.edu>
Reply-To: sl@van-bc.UUCP (Stuart Lynne)
Organization: Public Access Network, Vancouver, BC.
Lines: 27

In article <3842@watcgl.waterloo.edu> tbray@watsol.waterloo.edu (Tim Bray) writes:
>that Unix can do a maximum of 30 disk I/O's a second".  Somebody else remarked
>that that figure had been remarkably constant for quite some time.  Somebody
>else proposed that it was a fundamental law of Computer Science.  (Of course,
>we are poor peons restricted to the use of Vaxes and Suns).

Probably related to your average seek time plus rotational delay plus data
transfer. 

On most popular, extant Unix systems 20 - 30 ms is a reasonable figure
for average seek. Average rotational latency is 8.5 ms. Transfer time for a
one sector, say about 1 ms. 

Given a fast 20 ms drive, you probably should approach 30 disk I/O's per
second. 

Given a slow 30 ms drive, probably closer to 25, 40 ms about 20.

Other factors which will help are controllers which will overlap seeks;
multiple disk's to localize file accesses (allowing average seeks times to
decline); larger block sizes (actually getting the information in is only a
small part of the battle, getting there is the largest component for small
random reads).


-- 
{ihnp4!alberta!ubc-vision,uunet}!van-bc!Stuart.Lynne Vancouver,BC,604-937-7532