From: Manfred Spraul <manfred@colorfullife.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: markw@osdl.org
Cc: josh@agliodbs.com
Cc: Q@ping.be
Cc: pgman@candle.pha.pa.us
Cc: markir@paradise.net.nz
Cc: pgsql-performance@postgresql.org
Cc: pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] fsync method checking
Date: Thu, 25 Mar 2004 07:21:35 +0100
Message-ID: <40627A6F.9010202@colorfullife.com> (raw)
In-Reply-To: <6391.1079977274@sss.pgh.pa.us>
References: <200403221734.i2MHYGE01546@mail.osdl.org>
<6391.1079977274@sss.pgh.pa.us>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: manfred@colorfullife.com, tgl@sss.pgh.pa.us, markw@osdl.org, josh@agliodbs.com, Q@ping.be, pgman@candle.pha.pa.us, markir@paradise.net.nz, pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] fsync method checking
In-Reply-To: <40627A6F.9010202@colorfullife.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox