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 22:09:51 +0100
Message-ID: <20040318210951.GA8784@ping.be> (raw)
In-Reply-To: <200403182034.i2IKYLp27844@candle.pha.pa.us>
References: <20040318202621.GB8330@ping.be>
<200403182034.i2IKYLp27844@candle.pha.pa.us>
On Thu, Mar 18, 2004 at 03:34:21PM -0500, Bruce Momjian wrote:
> Kurt Roeckx wrote:
> > Here are my results on Linux 2.6.1 using cvs version 1.7.
> >
> > Those times with > 20 seconds, you really hear the disk go crazy.
> >
> > And I have the feeling something must be wrong. Those results
> > are reproducible.
> >
>
> Wow, your O_SYNC times are great. Where can I buy some? :-)
>
> Anyway, we do need to find a way to test this because obviously there is
> huge platform variability.
New results with version 1.8:
Simple write timing:
write 0.150613
Compare fsync times on write() and non-write() descriptor:
(If the times are similar, fsync() can sync data written
on a different descriptor.)
write, fsync, close 9.170472
write, close, fsync 8.851715
Compare one o_sync write to two:
one 16k o_sync write 2.617860
two 8k o_sync writes 2.563437
Compare file sync methods with one 8k write:
(o_dsync unavailable)
open o_sync, write 1.031721
write, fdatasync 25.599010
write, fsync, 26.192824
Compare file sync methods with 2 8k writes:
(The fastest should be used for wal_sync_method)
(o_dsync unavailable)
open o_sync, write 2.268718
write, fdatasync 27.029396
write, fsync, 27.399243
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: <20040318210951.GA8784@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