pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Zeugswetter Andreas SB SD <ZeugswetterA@spardat.at>
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 12:34:36 -0500 (EST)
Message-ID: <200403181734.i2IHYaR29308@candle.pha.pa.us> (raw)
In-Reply-To: <46C15C39FEB2C44BA555E356FBCD6FA40184CF68@m0114.s-mxs.net>


I have updated my program with your suggested changes and put in
src/tools/fsync.  Please see how you like it.

---------------------------------------------------------------------------

Zeugswetter Andreas SB SD wrote:
> 
> > Running the attached test program shows on BSD/OS 4.3:
> > 
> > 	write                  0.000360
> > 	write & fsync          0.001391
> 
> I think the "write & fsync" pays for the previous "write" test (same filename).
> 
> > 	write, close & fsync   0.001308
> > 	open o_fsync, write    0.000924
> 
> I have tried to modify the program to more closely resemble WAL 
> writes (all writes to WAL are 8k), the file is usually already open, 
> and test larger (16k) transactions.
> 
> zeu@a82101002:~> test_sync1
> write                      0.000625
> write & fsync              0.016748
> write & fdatasync          0.006650
> write, close & fsync       0.017084
> write, close & fdatasync   0.006890
> open o_dsync, write        0.015997
> open o_dsync, one write    0.007128
> 
> For the last line xlog.c would need to be modified, but the measurements
> seem to imply that it is only worth it on platforms that have O_DSYNC
> but not fdatasync.  
> 
> Andreas

Content-Description: test_sync1.c

[ Attachment, skipping... ]

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073



view thread (42+ messages)  latest in thread

Message-ID: <200403181734.i2IHYaR29308@candle.pha.pa.us>
Permalink:  ../200403181734.i2IHYaR29308@candle.pha.pa.us/
Also on:    postgresql.org/message-id/200403181734.i2IHYaR29308@candle.pha.pa.us

 · 

reply

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: pgman@candle.pha.pa.us, ZeugswetterA@spardat.at, markir@paradise.net.nz, pgsql-hackers@postgresql.org
  Subject: Re: [HACKERS] fsync method checking
  In-Reply-To: <200403181734.i2IHYaR29308@candle.pha.pa.us>

* 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