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 9256A53700 for ; Fri, 15 Apr 2005 21:58:34 -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 80708-07 for ; Sat, 16 Apr 2005 00:58:23 +0000 (GMT) Received: from sccrmhc12.comcast.net (sccrmhc12.comcast.net [204.127.202.56]) by svr1.postgresql.org (Postfix) with ESMTP id 6F1FA53210 for ; Fri, 15 Apr 2005 21:58:22 -0300 (ADT) Received: from sysexperts.com (c-24-6-183-218.hsd1.ca.comcast.net[24.6.183.218]) by comcast.net (sccrmhc12) with ESMTP id <200504160058260120057et7e>; Sat, 16 Apr 2005 00:58:26 +0000 Received: from localhost (localhost [127.0.0.1]) (uid 1000) by filer with local; Fri, 15 Apr 2005 17:58:25 -0700 id 000C40BE.42606331.00006582 Date: Fri, 15 Apr 2005 17:58:25 -0700 From: Kevin Brown To: pgsql-performance@postgresql.org Subject: Re: How to improve db performance with $7K? Message-ID: <20050416005824.GG19518@filer> Mail-Followup-To: Kevin Brown , pgsql-performance@postgresql.org References: <20050406224102.GM93835@decibel.org> <33c6269f0504061732195f6ae4@mail.gmail.com> <87wtrfmgt5.fsf@stark.xeocode.com> <13449.1112847297@sss.pgh.pa.us> <20050414055655.GB19518@filer> <878y3lj23o.fsf@stark.xeocode.com> <20050414083608.GC19518@filer> <446.1113489854@sss.pgh.pa.us> <20050415020337.GD19518@filer> <9fde2d603a18b53b5b3f22ad47f3a064@khera.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline In-Reply-To: <9fde2d603a18b53b5b3f22ad47f3a064@khera.org> Organization: Frobozzco International User-Agent: Mutt/1.5.8i X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.05 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200504/373 X-Sequence-Number: 11770 Vivek Khera wrote: > > On Apr 14, 2005, at 10:03 PM, Kevin Brown wrote: > > >Now, bad block remapping destroys that guarantee, but unless you've > >got a LOT of bad blocks, it shouldn't destroy your performance, right? > > > > ALL disks have bad blocks, even when you receive them. you honestly > think that these large disks made today (18+ GB is the smallest now) > that there are no defects on the surfaces? Oh, I'm not at all arguing that you won't have bad blocks. My argument is that the probability of any given block read or write operation actually dealing with a remapped block is going to be relatively small, unless the fraction of bad blocks to total blocks is large (in which case you basically have a bad disk). And so the ability to account for remapped blocks shouldn't itself represent a huge improvement in overall throughput. -- Kevin Brown kevin@sysexperts.com