Received: from localhost (unknown [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id BD3E32E0192 for ; Tue, 29 Jan 2008 13:14:08 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 02366-03 for ; Tue, 29 Jan 2008 13:14:05 -0400 (AST) Received: from gwmta.wicourts.gov (gwmta.wicourts.gov [165.219.244.99]) by postgresql.org (Postfix) with ESMTP id 712152E0129 for ; Tue, 29 Jan 2008 13:14:05 -0400 (AST) Received: from Courts-MTA by gwmta.wicourts.gov with Novell_GroupWise; Tue, 29 Jan 2008 11:14:04 -0600 Message-Id: <479F0A72.EE98.0025.0@wicourts.gov> X-Mailer: Novell GroupWise Internet Agent 7.0.2 Date: Tue, 29 Jan 2008 11:13:54 -0600 From: "Kevin Grittner" To: "Gregory Stark" Cc: "Matthew" , "Mark Mielke" , Subject: Re: RAID arrays and performance References: <87lk8aiqf3.fsf@oxford.xeocode.com> <475559F4.7060104@mark.mielke.cc> <4755648C.90905@mark.mielke.cc> <87bq96ii3b.fsf@oxford.xeocode.com> <4755810E.4000707@mark.mielke.cc> <87zlwq6yz9.fsf@oxford.xeocode.com> <87bq74vfys.fsf@oxford.xeocode.com> <877ihsvdcb.fsf@oxford.xeocode.com> <479EFE9A.EE98.0025.0@wicourts.gov> <873asginrz.fsf@stark.xeocode.com> In-Reply-To: <873asginrz.fsf@stark.xeocode.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200801/294 X-Sequence-Number: 28533 >>> On Tue, Jan 29, 2008 at 10:45 AM, in message <873asginrz.fsf@stark.xeocode.com>, Gregory Stark = wrote:=20 =20 > Well consider when you've reached n-1 drives; the expected number of = requests > before you hit the 1 idle drive remaining out of n would be n requests. = When > you're at n-2 the expected number of requests before you hit either of = the=20 > two > idle drives would be n/2. And so on. The last term of n/n would be the = first > i/o when all the drives are idle and you obviously only need one i/o to = hit=20 > an > idle drive. =20 You're right. Perhaps the reason more requests continue to improve performance is that a smart controller will move across the tracks and satisfy the pending requests in the most efficient order? =20 -Kevin =20