*BSD News Article 7563


Return to BSD News archive

Path: sserve!manuel.anu.edu.au!munnari.oz.au!sgiblab!swrinde!zaphod.mps.ohio-state.edu!magnus.acs.ohio-state.edu!usenet.ins.cwru.edu!agate!agate.berkeley.edu!cgd
From: cgd@eden.CS.Berkeley.EDU (Chris G. Demetriou)
Newsgroups: comp.unix.bsd
Subject: Re: bonnie i/o test results
Date: 6 Nov 92 23:28:22
Organization: Kernel Hackers 'r' Us
Lines: 69
Message-ID: <CGD.92Nov6232822@eden.CS.Berkeley.EDU>
References: <1992Nov6.144749.26760@ntuix.ntu.ac.sg>
NNTP-Posting-Host: eden.cs.berkeley.edu
In-reply-to: eoahmad@ntuix.ntu.ac.sg's message of Fri, 6 Nov 1992 14:47:49 GMT


LOOK, I'M SURE I'M NOT THE ONLY ONE WHO'S SICK OF SEEING BENCHMARKS WITH
ABSOLUTELY NO TECHNICAL MERIT.

(and yes, i had to scream.)

In article <1992Nov6.144749.26760@ntuix.ntu.ac.sg> eoahmad@ntuix.ntu.ac.sg (Othman Ahmad) writes:

   Julian 486/50 16M RAM, bustek SCSI-2 disk,

		 -------Sequential Output-------- ---Sequential Input-- --Random--
		 -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks---
   Machine    MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU  /sec %CPU
	      32   405 48.2   389  8.4   152  5.6   505 53.1   461 10.3  20.0  5.0

   My machine 386/25 8M RAM , IDE Maxtor 200M disk,

		 -------Sequential Output-------- ---Sequential Input-- --Random--
		 -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks---
   Machine    MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU  /sec %CPU
	      16   121 99.2   350 15.6   190 17.7   108 99.8   454 16.4  25.9  8.9

   Just look at the Random seek figure, the smaller IDE is faster despite having
   more CPU load.



in terms of reading and writing, as you can see from your above stats,
Julian's SCSI disk generally kicks your IDE disk's butt.

The one stat you cite is average random seek time, and that's the probably
the *MOST* meaningless of all of the above stats.

why?  because i'll bet money that your maxtor 200 IDE is a 3.5" disk,
and i know that Julian's disk is 5.25".

I've got a 3.5" inch w/an average seek time of 12ms (which should get
me 83 seeks per second)...  what does that prove, in terms of SCSI vs.
IDE?

*NOTHING*

why?  because i'm pretty sure that they make the same disk w/ an IDE
controller.



PLEASE, before posting any more benchmarks:
	(1) learn about disk architecture.
		If you knew anything about it, you'd know
		that seek time is *disk* dependent, not
		controller dependent.

	(2) run the benchmarks on "equivalent" hardware.
		for instance, Maxtor 200M IDE vs. Maxtor 200M SCSI
		(i'd to the SCSI benchmark for you, but the only
		Maxtor 200M SCSI I have kicked off a few months ago...)


<sigh>

and now back to some driver hacking...

Chris
--
Chris G. Demetriou                                    cgd@cs.berkeley.edu

"Sometimes it is better to have twenty million instructions by
        Friday than twenty million instructions per second." -- Wes Clark