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 554A253AD5 for ; Thu, 7 Apr 2005 04:01:22 +0100 (BST) 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 93882-08 for ; Thu, 7 Apr 2005 03:01:12 +0000 (GMT) Received: from stark.xeocode.com (stark.xeocode.com [216.58.44.227]) by svr1.postgresql.org (Postfix) with ESMTP id 9E68053AE1 for ; Thu, 7 Apr 2005 04:01:03 +0100 (BST) Received: from localhost ([127.0.0.1] helo=stark.xeocode.com) by stark.xeocode.com with smtp (Exim 3.36 #1 (Debian)) id 1DJNGI-0004MM-00; Wed, 06 Apr 2005 23:00:54 -0400 To: Alex Turner Cc: "Jim C. Nasby" , William Yu , pgsql-performance@postgresql.org Subject: Re: How to improve db performance with $7K? References: <424840AE.3050200@sfnet.cc> <42494741.7060806@fastcrypt.com> <33c6269f0504040643317b69cd@mail.gmail.com> <42515198.9090903@sfnet.cc> <33c6269f05040412126b5bc719@mail.gmail.com> <33c6269f050406083533d2045d@mail.gmail.com> <33c6269f050406151241b01148@mail.gmail.com> <20050406224102.GM93835@decibel.org> <33c6269f0504061732195f6ae4@mail.gmail.com> In-Reply-To: <33c6269f0504061732195f6ae4@mail.gmail.com> From: Greg Stark Organization: The Emacs Conspiracy; member since 1992 Date: 06 Apr 2005 23:00:54 -0400 Message-ID: <87wtrfmgt5.fsf@stark.xeocode.com> Lines: 23 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.009 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200504/139 X-Sequence-Number: 11536 Alex Turner writes: > SATA gives each drive it's own channel, but you have to share in SCSI. > A SATA controller typicaly can do 3Gb/sec (384MB/sec) per drive, but > SCSI can only do 320MB/sec across the entire array. SCSI controllers often have separate channels for each device too. In any case the issue with the IDE protocol is that fundamentally you can only have a single command pending. SCSI can have many commands pending. This is especially important for a database like postgres that may be busy committing one transaction while another is trying to read. Having several commands queued on the drive gives it a chance to execute any that are "on the way" to the committing transaction. However I'm under the impression that 3ware has largely solved this problem. Also, if you save a few dollars and can afford one additional drive that additional drive may improve your array speed enough to overcome that inefficiency. -- greg