X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 9D5BDDA7F3 for ; Mon, 21 Nov 2005 16:04:02 -0400 (AST) 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 09420-10 for ; Mon, 21 Nov 2005 20:04:00 +0000 (GMT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from svr2.postgresql.org (svr2.postgresql.org [65.19.161.25]) by svr1.postgresql.org (Postfix) with ESMTP id 78FF4DA748 for ; Mon, 21 Nov 2005 16:03:56 -0400 (AST) Received: from flake.decibel.org (flake.decibel.org [67.100.216.10]) by svr2.postgresql.org (Postfix) with ESMTP id 5DDC6F0DA1 for ; Mon, 21 Nov 2005 16:59:27 +0000 (GMT) Received: by flake.decibel.org (Postfix, from userid 1001) id D93D51529A; Mon, 21 Nov 2005 10:59:24 -0600 (CST) Date: Mon, 21 Nov 2005 10:59:24 -0600 From: "Jim C. Nasby" To: Mario Splivalo Cc: pgsql-admin@postgresql.org Subject: Re: Server Hardware Configuration Message-ID: <20051121165924.GT19279@pervasive.com> References: <20051120175337.GP19279@pervasive.com> <1132565676.8689.9.camel@ekim> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1132565676.8689.9.camel@ekim> X-Operating-System: FreeBSD 4.11-RELEASE-p10 i386 X-Distributed: Join the Effort! http://www.distributed.net User-Agent: Mutt/1.5.9i X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.021 required=5 tests=[AWL=0.021] X-Spam-Score: 0.021 X-Spam-Level: X-Archive-Number: 200511/287 X-Sequence-Number: 19660 On Mon, Nov 21, 2005 at 10:34:36AM +0100, Mario Splivalo wrote: > > RAID5 generally doesn't make for a fast database. The problem is that > > there is a huge amount of overhead everytime you go to write something > > out to a RAID5 array. With careful tuning of the background writer you > > might be able to avoid some of that penalty, though your read > > performance will likely still be affected by the write overhead. > > RAID5 was not ment to improve performance, but to minimize disaster and > downtime when your hard disk dies. We're using RAID5 with postgres. In > the last 3 years we changed 5 disks, but the system downtime was zero > minutes. And the same would have been true with RAID10. In fact, RAID10 is more reliable than RAID5; depending on what drives fail it's possible to lose up to half of a RAID10 array without any data loss. If you ever lose more than 2 drives at once with RAID5, your data is gone. -- Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com Pervasive Software http://pervasive.com work: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461