X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 04F80D1B4B0 for ; Thu, 4 Mar 2004 00:52:11 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 55183-04 for ; Wed, 3 Mar 2004 20:52:16 -0400 (AST) Received: from anchor-post-30.mail.demon.net (anchor-post-30.mail.demon.net [194.217.242.88]) by svr1.postgresql.org (Postfix) with ESMTP id 1E484D1CA78 for ; Wed, 3 Mar 2004 20:52:07 -0400 (AST) Received: from tmsl-adsl.demon.co.uk ([80.177.114.181] helo=bacon.tmsl.demon.co.uk) by anchor-post-30.mail.demon.net with esmtp (Exim 3.35 #1) id 1Ayh5w-0004Yl-0U; Thu, 04 Mar 2004 00:52:12 +0000 Date: Thu, 4 Mar 2004 00:52:08 +0000 From: Paul Thomas To: "scott . marlowe" Cc: "pgsql-performance @ postgresql . org" Subject: Re: Scaling further up Message-ID: <20040304005208.A25816@bacon> References: <20040303085718.A24535@bacon> Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset=ISO-8859-1 In-Reply-To: ; from scott.marlowe@ihs.com on Wed, Mar 03, 2004 at 18:23:11 +0000 X-Mailer: Balsa 1.2.3 Lines: 35 X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/55 X-Sequence-Number: 5911 On 03/03/2004 18:23 scott.marlowe wrote: > [snip] > There are three factors that affect how fast you can get to the next > sector: > > seek time > settle time > rotational latency > > Most drives only list the first, and don't bother to mention the other > two. Ah yes, one of my (very) few still functioning brain cells was nagging about another bit of time in the equation :) > On many modern drives, the seek times are around 5 to 10 milliseconds. > [snip] Going back to the OPs posting about random_page_cost, imagine I have 2 servers identical in every way except the disk drive. Server A has a 10K rpm drive and server B has a 15K rpm drive. Seek/settle times aren't spectacularly different between the 2 drives. I'm wondering if drive B might actually merit a _higher_ random_page_cost than drive A as, once it gets settled on a disk track, it can suck the data off a lot faster. opinions/experiences anyone? -- Paul Thomas +------------------------------+---------------------------------------------+ | Thomas Micro Systems Limited | Software Solutions for the Smaller Business | | Computer Consultants | http://www.thomas-micro-systems-ltd.co.uk | +------------------------------+---------------------------------------------+