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 EC4133A1D17 for ; Fri, 14 Jan 2005 18:47:44 +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 01990-06 for ; Fri, 14 Jan 2005 18:47:40 +0000 (GMT) Received: from stark.xeocode.com (gsstark.mtl.istop.com [66.11.160.162]) by svr1.postgresql.org (Postfix) with ESMTP id 3307E3A1D43 for ; Fri, 14 Jan 2005 18:47:40 +0000 (GMT) Received: from localhost ([127.0.0.1] helo=stark.xeocode.com) by stark.xeocode.com with smtp (Exim 3.36 #1 (Debian)) id 1CpWTv-0001jN-00; Fri, 14 Jan 2005 13:47:35 -0500 To: Josh Berkus Cc: pgsql-performance@postgresql.org, "Merlin Moncure" , Subject: Re: which dual-CPU hardware/OS is fastest for PostgreSQL? References: <6EE64EF3AB31D5448D0007DD34EEB3412A75B4@Herge.rcsinc.local> <200501140936.08654.josh@agliodbs.com> In-Reply-To: <200501140936.08654.josh@agliodbs.com> From: Greg Stark Organization: The Emacs Conspiracy; member since 1992 Date: 14 Jan 2005 13:47:34 -0500 Message-ID: <874qhjvoe1.fsf@stark.xeocode.com> Lines: 30 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.055 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200501/193 X-Sequence-Number: 9883 Josh Berkus writes: > Merlin, > > > I think the danger about SATA is that many SATA components are not > > server quality, so you have to be more careful about what you buy. For > > example, you can't just assume your SATA backplane has hot swap lights > > (got bit by this one myself, heh). > > Yeah, that's my big problem with anything IDE. My personal experience of > failure rates for IDE drives, for example, is about 1 out of 10 fails in > service before it's a year old; SCSI has been more like 1 out of 50. Um. I'm pretty sure the actual hardware is just the same stuff. It's just the interface electronics that change. > Also, while I've seen benchmarks like Escalade's, my real-world experience has > been that the full bi-directional r/w of SCSI means that it takes 2 SATA > drives to equal one SCSI drive in a heavy r/w application. However, ODSL is > all SCSI so I don't have any numbers to back that up. Do we know that these SATA/IDE controllers and drives don't "lie" about fsync the way most IDE drives do? Does the controller just automatically disable the write caching entirely? I don't recall, did someone have a program that tested the write latency of a drive to test this? -- greg