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 772B9539D4 for ; Wed, 6 Apr 2005 08:30:54 +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 52191-02 for ; Wed, 6 Apr 2005 07:30:50 +0000 (GMT) Received: from floppy.pyrenet.fr (news.pyrenet.fr [194.116.145.2]) by svr1.postgresql.org (Postfix) with ESMTP id 96F6C539CF for ; Wed, 6 Apr 2005 08:30:48 +0100 (BST) Received: by floppy.pyrenet.fr (Postfix, from userid 106) id 1E63530952; Wed, 6 Apr 2005 09:30:30 +0200 (MET DST) From: William Yu X-Newsgroups: pgsql.performance Subject: Re: How to improve db performance with $7K? Date: Wed, 06 Apr 2005 00:30:44 -0700 Organization: Hub.Org Networking Services Lines: 24 Message-ID: References: <42443863.4040302@sfnet.cc> <42453273.2060509@turtle-entertainment.de> <200503261255.59007.josh@agliodbs.com> <42455DEC.2080301@sfnet.cc> <1112049794.23284.29.camel@localhost.localdomain> <424840AE.3050200@sfnet.cc> <42494741.7060806@fastcrypt.com> <33c6269f0504040643317b69cd@mail.gmail.com> <42515198.9090903@sfnet.cc> <33c6269f05040412126b5bc719@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@news.hub.org User-Agent: Mozilla Thunderbird 1.0 (X11/20041206) X-Accept-Language: en-us, en In-Reply-To: <33c6269f05040412126b5bc719@mail.gmail.com> To: pgsql-performance@postgresql.org X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests= X-Spam-Level: X-Archive-Number: 200504/91 X-Sequence-Number: 11488 Alex Turner wrote: > I'm no drive expert, but it seems to me that our write performance is > excellent. I think what most are concerned about is OLTP where you > are doing heavy write _and_ heavy read performance at the same time. > > Our system is mostly read during the day, but we do a full system > update everynight that is all writes, and it's very fast compared to > the smaller SCSI system we moved off of. Nearly a 6x spead > improvement, as fast as 900 rows/sec with a 48 byte record, one row > per transaction. I've started with SATA in a multi-read/multi-write environment. While it ran pretty good with 1 thread writing, the addition of a 2nd thread (whether reading or writing) would cause exponential slowdowns. I suffered through this for a week and then switched to SCSI. Single threaded performance was pretty similar but with the advanced command queueing SCSI has, I was able to do multiple reads/writes simultaneously with only a small performance hit for each thread. Perhaps having a SATA caching raid controller might help this situation. I don't know. It's pretty hard justifying buying a $$$ 3ware controller just to test it when you could spend the same money on SCSI and have a guarantee it'll work good under multi-IO scenarios.