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 20520D1B97B; Thu, 25 Mar 2004 06:22:31 +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 64509-05; Thu, 25 Mar 2004 02:22:27 -0400 (AST) Received: from dbl.q-ag.de (dbl.q-ag.de [213.172.117.3]) by svr1.postgresql.org (Postfix) with ESMTP id 463F2D1E943; Thu, 25 Mar 2004 02:22:25 -0400 (AST) Received: from colorfullife.com (dbl [127.0.0.1]) by dbl.q-ag.de (8.12.3/8.12.3/Debian-6.6) with ESMTP id i2P6LZro004886; Thu, 25 Mar 2004 07:21:36 +0100 Message-ID: <40627A6F.9010202@colorfullife.com> Date: Thu, 25 Mar 2004 07:21:35 +0100 From: Manfred Spraul User-Agent: Mozilla/5.0 (X11; U; Linux i686; fr-FR; rv:1.4.1) Gecko/20031114 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tom Lane Cc: markw@osdl.org, josh@agliodbs.com, Q@ping.be, pgman@candle.pha.pa.us, markir@paradise.net.nz, pgsql-performance@postgresql.org, pgsql-hackers@postgresql.org Subject: Re: [HACKERS] fsync method checking References: <200403221734.i2MHYGE01546@mail.osdl.org> <6391.1079977274@sss.pgh.pa.us> In-Reply-To: <6391.1079977274@sss.pgh.pa.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/379 X-Sequence-Number: 6235 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 -- Manfred