X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id C72EFD1B488 for ; Fri, 12 Dec 2003 22:59:44 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 08281-06 for ; Fri, 12 Dec 2003 18:59:16 -0400 (AST) Received: from news.hub.org (news.hub.org [200.46.204.72]) by svr1.postgresql.org (Postfix) with ESMTP id 2BB05D1B4AD for ; Fri, 12 Dec 2003 18:59:14 -0400 (AST) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.12.9/8.12.9) with ESMTP id hBCMxDU6012627 for ; Fri, 12 Dec 2003 22:59:13 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.12.9/8.12.9/Submit) id hBCMjO55097997 for pgsql-performance@postgresql.org; Fri, 12 Dec 2003 22:45:24 GMT From: William Yu X-Newsgroups: comp.databases.postgresql.performance Subject: Re: Update on putting WAL on ramdisk/ Date: Fri, 12 Dec 2003 14:45:31 -0800 Organization: Hub.Org Networking Services Lines: 18 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@news.hub.org User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007 X-Accept-Language: en-us, en In-Reply-To: To: pgsql-performance@postgresql.org X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200312/209 X-Sequence-Number: 5069 Russell Garrett wrote: >>WAL on single drive: 7.990 rec/s >>WAL on 2nd IDE drive: 8.329 rec/s >>WAL on tmpfs: 13.172 rec/s >> >>A huge jump in performance but a bit scary having a WAL that can >>disappear at any time. I'm gonna workup a rsync script and do some >>power-off experiments to see how badly it gets mangled. > > > Surely this is just equivalent to disabling fsync? If you put a WAL on a > volatile file system, there's not a whole lot of point in having one at all. These tests were all with fsync off. And no, it's not equivalent to fsync off since the WAL is always written immediately regardless of fsync setting.