From owner-freebsd-questions@FreeBSD.ORG Thu Jun 29 19:30:01 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 217F716A403 for ; Thu, 29 Jun 2006 19:30:01 +0000 (UTC) (envelope-from chad@shire.net) Received: from hobbiton.shire.net (mail.shire.net [166.70.252.250]) by mx1.FreeBSD.org (Postfix) with ESMTP id 00CA2447AC for ; Thu, 29 Jun 2006 19:29:55 +0000 (GMT) (envelope-from chad@shire.net) Received: from [67.171.127.191] (helo=[192.168.99.68]) by hobbiton.shire.net with esmtpa (Exim 4.51) id 1Fw2D5-000MWf-4k; Thu, 29 Jun 2006 13:29:55 -0600 In-Reply-To: <226ae0c60606290741l660729e5hb1649b2f0aac7ea1@mail.gmail.com> References: <226ae0c60606290640p5855b367l2d8d894bff3e0b86@mail.gmail.com> <70e8236f0606290725y48f1cbffi3d9f969ae3db505f@mail.gmail.com> <226ae0c60606290741l660729e5hb1649b2f0aac7ea1@mail.gmail.com> Mime-Version: 1.0 (Apple Message framework v750) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <9E5F3BAE-838A-493A-9B45-33275AFC10E9@shire.net> Content-Transfer-Encoding: 7bit From: "Chad Leigh -- Shire.Net LLC" Date: Thu, 29 Jun 2006 13:29:54 -0600 To: David Robillard X-Mailer: Apple Mail (2.750) X-SA-Exim-Connect-IP: 67.171.127.191 X-SA-Exim-Mail-From: chad@shire.net X-SA-Exim-Scanned: No (on hobbiton.shire.net); SAEximRunCond expanded to false Cc: Joao Barros , FreeBSD Questions Mailing List Subject: Re: Are hardware vendors starting to bail on FreeBSD ... ? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Jun 2006 19:30:01 -0000 On Jun 29, 2006, at 8:41 AM, David Robillard wrote: > Well, there are two issues here: access time (rpm) and storage > capacity (GB). The access time deals with rotational speed of the > drives (rpm) while storage capacity (GB) does not care how fast the > drive spins. There is a third and that is bit density. The reason that that is important is that it can compensate for a slower drive (rotational speed). If a fast drive with lower bit density has to rotate X rotation to get to the data, a higher bit density drive will usually have to rotate something less than X because the data is more dense. In simple terms (these numbers are made up to illustrate this and have no bearing on real numbers except that the concept holds: a fast RPM with lower bit density might have 1GB per cylinder and hence say 2/3 of a rotation might be needed to get data X. A higher density drive might have 6GB per cylinder so needs only, say 1/9 of a slower rotation to get to the same data). This was amply illustrated by some 500GB SATA benchmark I read that had it equaling some much faster RPM drives for access time with much lower bit density. Other factors play in here as well but hopefully you get the idea. Chad --- Chad Leigh -- Shire.Net LLC Your Web App and Email hosting provider chad at shire.net