Xref: utzoo comp.protocols.nfs:1879 comp.arch:21246
Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!uunet!bellcore!messy!mo
From: mo@messy.bellcore.com (Michael O'Dell)
Newsgroups: comp.protocols.nfs,comp.arch
Subject: Re: disk queues of length zero.....
Message-ID: <1991Mar6.003008.9131@bellcore.bellcore.com>
Date: 6 Mar 91 00:30:08 GMT
References: <28975@cs.yale.edu> <PCG.91Feb28195347@odin.cs.aber.ac.uk> <PCG.91Mar4210505@aberdb.cs.aber.ac.uk> <1991Mar5.223443.21187@ns.uoregon.edu>
Sender: usenet@bellcore.bellcore.com (Poster of News)
Reply-To: mo@bellcore.com (Michael O'Dell)
Organization: Center for Chaotic Repeatabilty
Lines: 15

I know *I* have seen servers with much longer disk queues.

For example -

	Assume you memory map and create large file on a machine with lots
	of free memory.  Say you write 50 megabytes.  You now close
	the file and hence ask for it to really go to disk.
	WHAM! 50 megabytes goes on the disk queue.  Yes this does happen,
	and boy, is the poor dweeb at some other terminal who just
	typed "ls" on the same filesystem really screwed.

There are many more anomolies out there when the machine and the memory
get sufficiently fast and large....

	-Mike