X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id CC464D1ECCB; Thu, 25 Mar 2004 17:17:27 +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 90261-03; Thu, 25 Mar 2004 13:17:31 -0400 (AST) Received: from mail.osdl.org (fw.osdl.org [65.172.181.6]) by svr1.postgresql.org (Postfix) with ESMTP id 6B53AD1EC79; Thu, 25 Mar 2004 13:17:25 -0400 (AST) Received: from osdl.org (markw@ibm-b.pdx.osdl.net [172.20.1.51]) by mail.osdl.org (8.11.6/8.11.6) with ESMTP id i2PHGh222327; Thu, 25 Mar 2004 09:16:44 -0800 Message-Id: <200403251716.i2PHGh222327@mail.osdl.org> Date: Thu, 25 Mar 2004 09:16:40 -0800 (PST) From: markw@osdl.org Subject: Re: [HACKERS] fsync method checking To: manfred@colorfullife.com Cc: tgl@sss.pgh.pa.us, josh@agliodbs.com, Q@ping.be, pgman@candle.pha.pa.us, markir@paradise.net.nz, pgsql-performance@postgresql.org, pgsql-hackers@postgresql.org In-Reply-To: <40627A6F.9010202@colorfullife.com> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/358 X-Sequence-Number: 6214 On 25 Mar, Manfred Spraul wrote: > Tom Lane wrote: > >>markw@osdl.org writes: >> >> >>>I could certainly do some testing if you want to see how DBT-2 does. >>>Just tell me what to do. ;) >>> >>> >> >>Just do some runs that are identical except for the wal_sync_method >>setting. Note that this should not have any impact on SELECT >>performance, only insert/update/delete performance. >> >> > I've made a test run that compares fsync and fdatasync: The performance > was identical: > - with fdatasync: > > http://khack.osdl.org/stp/290607/ > > - with fsync: > http://khack.osdl.org/stp/290483/ > > I don't understand why. Mark - is there a battery backed write cache in > the raid controller, or something similar that might skew the results? > The test generates quite a lot of wal traffic - around 1.5 MB/sec. > Perhaps the writes are so large that the added overhead of syncing the > inode is not noticable? > Is the pg_xlog directory on a seperate drive? > > Btw, it's possible to request such tests through the web-interface, see > http://www.osdl.org/lab_activities/kernel_testing/stp/script_param.html We have 2 Adaptec 2200s controllers, without the battery backed add-on, connected to four 10-disk arrays in those systems. I can't think of anything off hand that would skew the results. The pg_xlog directory is not on a separate drive. I haven't found the best way to lay out of the drives on those systems yet, so I just have everything on a 28 drive lvm2 volume. Mark