Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!hellgate.utah.edu!dog.ee.lbl.gov!ucbvax!agate!usenet.ins.cwru.edu!gatech!udel!haven!ni.umd.edu!sayshell.umd.edu!louie
From: louie@sayshell.umd.edu (Louis A. Mamakos)
Newsgroups: comp.sys.next
Subject: Re: 400meg drive in NextStation is fast!
Message-ID: <1991Feb28.165239.4871@ni.umd.edu>
Date: 28 Feb 91 16:52:39 GMT
References: <6708@idunno.Princeton.EDU>
Sender: usenet@ni.umd.edu (USENET News System)
Organization: University of Maryland, College Park
Lines: 15
Nntp-Posting-Host: sayshell.umd.edu

In article <6708@idunno.Princeton.EDU> paul@phoenix.Princeton.EDU (Paul Lansky) writes:
>We just got a NextStation with a 400 meg hard drive, and I did 
>ramirez> temp/ time dd if=piano1.snd of=/dev/null bs=32768
>581+0 records in
>581+0 records out
>0.0u 9.0s 0:17 53% 0+0k 2332+0io 0pf+0w

How much of this file was already lying about in kernel buffers?  I don't 
think that you are only measuring disk performance, but also the effect of
Mach's VM and file mapping.

For those of you running MH:  do a 'scan' of a folder and note how long it
takes.  Do another scan, and notice that it runs MUCH faster than before..

louie