From: Kurt Roeckx <Q@ping.be>
To: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Mark Kirkwood <markir@paradise.net.nz>
Cc: pgsql-performance@postgresql.org, PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: [HACKERS] fsync method checking
Date: Thu, 18 Mar 2004 21:03:59 +0100
Message-ID: <20040318200359.GA8330@ping.be> (raw)
In-Reply-To: <200403181922.i2IJMAd16258@candle.pha.pa.us>
References: <20040318191840.GA7088@ping.be>
<200403181922.i2IJMAd16258@candle.pha.pa.us>
On Thu, Mar 18, 2004 at 02:22:10PM -0500, Bruce Momjian wrote:
>
> OK, what better test do you suggest? Right now, there has been no
> testing of these.
I suggest you start by doing atleast preallocating a 16 MB file
and do the tests on that, to atleast be somewhat simular to what
WAL does.
I have no idea what the access pattern is for normal WAL
operations or how many times it gets synched. Does it only do
f(data)sync() at commit time, or for every block it writes?
I think if you write more data you'll see more differences
between O_(D)SYNC and f(data)sync().
I guess it can depend on if you have lots of small transactions,
or more big ones.
Atleast try to make something that covers different access
patterns.
Kurt
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: Q@ping.be, pgman@candle.pha.pa.us, tgl@sss.pgh.pa.us, markir@paradise.net.nz, pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] fsync method checking
In-Reply-To: <20040318200359.GA8330@ping.be>
* 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