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 E9F695321A for ; Mon, 28 Mar 2005 22:36:23 +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 87650-06 for ; Mon, 28 Mar 2005 21:36:14 +0000 (GMT) Received: from stark.xeocode.com (stark.xeocode.com [216.58.44.227]) by svr1.postgresql.org (Postfix) with ESMTP id E24CE53205 for ; Mon, 28 Mar 2005 22:36:13 +0100 (BST) Received: from localhost ([127.0.0.1] helo=stark.xeocode.com) by stark.xeocode.com with smtp (Exim 3.36 #1 (Debian)) id 1DG1u3-0006IG-00; Mon, 28 Mar 2005 16:36:07 -0500 To: jd@commandprompt.com Cc: Greg Stark , Merlin Moncure , alex@neteconomist.com, pgsql-performance@postgresql.org Subject: Re: which dual-CPU hardware/OS is fastest for PostgreSQL? References: <6EE64EF3AB31D5448D0007DD34EEB3412A75B4@Herge.rcsinc.local> <8764zb353a.fsf@stark.xeocode.com> <1112043428.26232.43.camel@jd2.commandprompt.com> In-Reply-To: <1112043428.26232.43.camel@jd2.commandprompt.com> From: Greg Stark Organization: The Emacs Conspiracy; member since 1992 Date: 28 Mar 2005 16:36:06 -0500 Message-ID: <87wtrr1mih.fsf@stark.xeocode.com> Lines: 21 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.011 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200503/615 X-Sequence-Number: 11320 "Joshua D. Drake" writes: > > I assume AMCC == 3ware now? > > > > Has anyone verified that fsync is safe on these controllers? Ie, that they > > aren't caching writes and "lying" about the write completing like IDE > > drives often do by default? > > The higher end AMCC/3ware controllers actually warn you about using > write-cache. You have to explicitly turn it on within the controller > bios. Well that's a good sign. But if they're using SATA drives my concern is that the drives themselves may be doing some caching on their own. Has anyone verified that the controllers are disabling the drive cache or issuing flushes or doing something else to be sure to block the drives from caching writes? -- greg