X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 0DF43539D7 for ; Fri, 15 Apr 2005 07:14:04 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 45958-05 for ; Fri, 15 Apr 2005 10:13:59 +0000 (GMT) Received: from boutiquenumerique.com (boutiquenumerique.com [82.67.9.10]) by svr1.postgresql.org (Postfix) with ESMTP id D22E55407D for ; Fri, 15 Apr 2005 07:13:58 -0300 (ADT) Received: (qmail 24380 invoked from network); 15 Apr 2005 12:14:04 +0200 Received: from unknown (HELO localhost) (boutiquenumerique-lists@192.168.0.4) by boutiquenumerique.com with SMTP; 15 Apr 2005 12:14:04 +0200 To: "Alex Turner" , "Kevin Brown" , pgsql-performance@postgresql.org Subject: Re: How to improve db performance with $7K? References: <33c6269f050414192472a58cf6@mail.gmail.com> <20050415020337.GD19518@filer> <446.1113489854@sss.pgh.pa.us> <20050414083608.GC19518@filer> <878y3lj23o.fsf@stark.xeocode.com> <20050414055655.GB19518@filer> <13449.1112847297@sss.pgh.pa.us> <87wtrfmgt5.fsf@stark.xeocode.com> <33c6269f0504061732195f6ae4@mail.gmail.com> <20050406224102.GM93835@decibel.org> Message-ID: Date: Fri, 15 Apr 2005 12:13:59 +0200 From: PFC Organization: =?iso-8859-15?Q?La_Boutique_Num=E9rique?= Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-15 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit In-Reply-To: <33c6269f050414192472a58cf6@mail.gmail.com> User-Agent: Opera M2(BETA2)/8.0 (Linux, build 987) X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.002 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200504/332 X-Sequence-Number: 11729 > platter compared to the rotational speed, which would agree with the > fact that you can read 70MB/sec, but it takes up to 13ms to seek. Actually : - the head has to be moved this time depends on the distance, for instance moving from a cylinder to the next is very fast (it needs to, to get good throughput) - then you have to wait for the disk to spin until the information you want comes in front of the head... statistically you have to wait a half rotation. And this does not depend on the distance between the cylinders, it depends on the position of the data in the cylinder. The more RPMs you have, the less you wait, which is why faster RPMs drives have faster seek (they must also have faster actuators to move the head)...