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 CC97F3A5CA1 for ; Wed, 26 Jan 2005 18:04:07 +0000 (GMT) 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 66484-02 for ; Wed, 26 Jan 2005 18:04:05 +0000 (GMT) Received: from davinci.ethosmedia.com (server227.ethosmedia.com [209.128.84.227]) by svr1.postgresql.org (Postfix) with ESMTP id E0D7B3A5C8F for ; Wed, 26 Jan 2005 18:04:05 +0000 (GMT) X-EthosMedia-Virus-Scanned: no infections found Received: from [63.195.55.98] (account josh@agliodbs.com HELO spooky) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.1.8) with ESMTP id 6953639 for pgsql-performance@postgresql.org; Wed, 26 Jan 2005 10:05:46 -0800 From: Josh Berkus Organization: Aglio Database Solutions To: pgsql-performance@postgresql.org Subject: Re: Ideal disk setup for Postgresql 7.4? Date: Wed, 26 Jan 2005 10:03:15 -0800 User-Agent: KMail/1.6.2 References: <41F63424.1060904@sfnet.cc> <200501251903.09734.josh@agliodbs.com> <41F6DBD8.2050008@sfnet.cc> In-Reply-To: <41F6DBD8.2050008@sfnet.cc> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200501261003.15267.josh@agliodbs.com> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.014 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200501/503 X-Sequence-Number: 10193 Steve, > Because the proprietary application running the business has not > certified on it. Unfortunately, I am at the mercy of their support in > case something goes wrong. FWIW, 7.4.6 is a binary, drop-in place upgrade for 7.4.2. And 7.4.2 has known bugs. However, I understand your situation. > Okay, thanks. Even with 7-disks? I trust that. Well, it's less bad with 7 disks than it is with 3, certainly. However,there is an obvious and quick gain to be had by splitting off the WAL logs onto their own disk resource ... up to 14%+ performance in some applications. > So, RAID 1+0 (sw) is > probably the best option. I've run sw RAID personally for years without > issue. I am a bit hesitant in doing sw RAID for a production server for > a database --- probably because its not my server. Any thoughts on sw > RAID for Postgresql? Yes. See my article for one. In generaly, SW RAID on BSD or Linux works well for PostgreSQL ... UNLESS your machine is already CPU-bound, in which case it's a bad idea. If you're hitting the CS bug, it's definitely a bad idea, because the SW RAID will increase context switching. So if your choice, on your system, is between sw RAID 10, and hw RAID 5, and you're having excessive CSes, I'd stick with the HW RAID. > Okay. Darn. While I don't write the queries for the application, I do > interact with the company frequently. Their considering moving the > queries into the database with PL/pgSQL. Currently their queries are > done through ProvIV development using ODBC. Will context switching be > minimized here by using PL/pgSQL? Won't make a difference, actually. Should improve performance in other ways, though, by reducing round-trip time on procedures. Feel free to recommend the company to this list. > Dual Xeon 2.8 CPUs with HT turned off. Yeah, thought it was a Xeon. -- Josh Berkus Aglio Database Solutions San Francisco