X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id AEA5D9DC9B6 for ; Sat, 24 Dec 2005 18:45:22 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 56893-03 for ; Sat, 24 Dec 2005 18:45:23 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from smtpauth08.mail.atl.earthlink.net (smtpauth08.mail.atl.earthlink.net [209.86.89.68]) by postgresql.org (Postfix) with ESMTP id 9C8359DC9B0 for ; Sat, 24 Dec 2005 18:45:19 -0400 (AST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=g3oH53x3Sc+dGXJoi40RMlusmhd9n579Q3lWJOWgs8kxqrvxcj8D8s0wmDm7uQRi; h=Received:Message-Id:X-Mailer:Date:To:From:Subject:In-Reply-To:References:Mime-Version:Content-Type:X-ELNK-Trace:X-Originating-IP; Received: from [70.22.244.95] (helo=ron-6d52adff2a6.earthlink.net) by smtpauth08.mail.atl.earthlink.net with asmtp (Exim 4.34) id 1EqI8f-00048n-Dd; Sat, 24 Dec 2005 17:45:21 -0500 Message-Id: <6.2.5.6.0.20051224172653.01dd4c08@earthlink.net> X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6 Date: Sat, 24 Dec 2005 17:45:20 -0500 To: David Lang ,pgsql-performance@postgresql.org From: Ron Subject: Re: What's the best hardver for PostgreSQL 8.1? In-Reply-To: References: <43A84D03.7090002@ritek.hu> <200512212209.50234.caseroj@comcast.net> <200512212231.55100.caseroj@comcast.net> <20051224135042.484c6e32.frank@wiles.org> <6.2.5.6.0.20051224161551.01dc5d98@earthlink.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-ELNK-Trace: acd68a6551193be5d780f4a490ca69563f9fea00a6dd62bcf681434346b101292c259b2d162116d6350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 70.22.244.95 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.392 required=5 tests=[AWL=-0.087, DNS_FROM_RFC_ABUSE=0.479] X-Spam-Score: 0.392 X-Spam-Level: X-Archive-Number: 200512/601 X-Sequence-Number: 16422 At 04:54 PM 12/24/2005, David Lang wrote: >raid 5 is bad for random writes as you state, but how does it do for >sequential writes (for example data mining where you do a large >import at one time, but seldom do other updates). I'm assuming a >controller with a reasonable amount of battery-backed cache. The issue with RAID 5 writes centers on the need to recalculate checksums for the ECC blocks distributed across the array and then write the new ones to physical media. Caches help, and the bigger the cache the better, but once you are doing enough writes fast enough (and that doesn't take much even with a few GBs of cache) the recalculate-checksums-and-write-new-ones overhead will decrease the write speed of real data. Bear in mind that the HD's _raw_ write speed hasn't been decreased. Those HD's are pounding away as fast as they can for you. Your _effective_ or _data level_ write speed is what decreases due to overhead. Side Note: people often forget the other big reason to use RAID 10 over RAID 5. RAID 5 is always only 2 HD failures from data loss. RAID 10 can lose up to 1/2 the HD's in the array w/o data loss unless you get unlucky and lose both members of a RAID 1 set. This can be seen as an example of the classic space vs. time trade off in performance tuning. You can use 2x the HDs you need and implement RAID 10 for best performance and reliability or you can dedicate less HD's to RAID and implement RAID 5 for less (write) performance and lower reliability. TANSTAAFL. Ron Peacetree