Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] fsync method checking

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: markw(at)osdl(dot)org
Cc: manfred(at)colorfullife(dot)com, tgl(at)sss(dot)pgh(dot)pa(dot)us, josh(at)agliodbs(dot)com,Q(at)ping(dot)be, markir(at)paradise(dot)net(dot)nz, pgsql-performance(at)postgresql(dot)org,pgsql-hackers(at)postgresql(dot)org
Subject: Re: [HACKERS] fsync method checking
Date: 2004-03-26 16:54:59
Message-ID: 200403261654.i2QGsxt04146@candle.pha.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-performance
markw(at)osdl(dot)org wrote:
> On 26 Mar, Manfred Spraul wrote:
> > markw(at)osdl(dot)org wrote:
> > 
> >>Compare file sync methods with one 8k write:
> >>        (o_dsync unavailable)  
> >>        open o_sync, write       6.270724
> >>        write, fdatasync        13.275225
> >>        write, fsync,           13.359847
> >>  
> >>
> > Odd. Which filesystem, which kernel? It seems fdatasync is broken and 
> > syncs the inode, too.
> 
> It's linux-2.6.5-rc1 with ext2 filesystems.

Would you benchmark open_sync for wal_sync_method too?

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

In response to

Responses

pgsql-performance by date

Next:From: markwDate: 2004-03-26 17:00:56
Subject: Re: [HACKERS] fsync method checking
Previous:From: markwDate: 2004-03-26 16:09:43
Subject: Re: [HACKERS] fsync method checking

pgsql-hackers by date

Next:From: Bruce MomjianDate: 2004-03-26 17:00:19
Subject: Re: Nested transaction proposal - take N (N > 2)
Previous:From: markwDate: 2004-03-26 16:09:43
Subject: Re: [HACKERS] fsync method checking

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group