pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Manfred Spraul <manfred@colorfullife.com>
To: Bruce Momjian <pgman@candle.pha.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: Fri, 12 Dec 2003 21:54:34 +0100
Message-ID: <3FDA2B0A.1060709@colorfullife.com> (raw)
In-Reply-To: <200312120649.hBC6nQR15608@candle.pha.pa.us>
References: <200312120649.hBC6nQR15608@candle.pha.pa.us>

Bruce Momjian wrote:

>	write                  0.000360
>	write & fsync          0.001391
>	write, close & fsync   0.001308
>	open o_fsync, write    0.000924
>  
>
That's 1 milliseconds vs. 1.3 milliseconds. Neither value is realistic - 
I guess the hw cache on and the os doesn't issue cache flush commands. 
Realistic values are probably 5 ms vs 5.3 ms - 6%, not 30%. How large is 
the syscall latency with BSD/OS 4.3?

One advantage of a seperate write and fsync call is better performance 
for the writes that are triggered within AdvanceXLInsertBuffer: I'm not 
sure how often that's necessary, but it's a write while holding both the 
WALWriteLock and WALInsertLock. If every write contains an implicit 
sync, that call would be much more expensive than necessary.

--
    Manfred




view thread (42+ messages)  latest in thread

Message-ID: <3FDA2B0A.1060709@colorfullife.com>
Permalink:  ../3FDA2B0A.1060709@colorfullife.com/
Also on:    postgresql.org/message-id/3FDA2B0A.1060709@colorfullife.com

 · 

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: manfred@colorfullife.com, pgman@candle.pha.pa.us, markir@paradise.net.nz, pgsql-hackers@postgresql.org
  Subject: Re: [HACKERS] fsync method checking
  In-Reply-To: <3FDA2B0A.1060709@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