Re: Proposed LogWriter Scheme, WAS: Potential Large Performance Gain in WAL synching

From: "Zeugswetter Andreas SB SD" <ZeugswetterA(at)spardat(dot)at>
To: "Curtis Faith" <curtis(at)galtair(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Pgsql-Hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Proposed LogWriter Scheme, WAS: Potential Large Performance Gain in WAL synching
Date: 2002-10-07 08:42:44
Message-ID: 46C15C39FEB2C44BA555E356FBCD6FA4961EB3@m0114.s-mxs.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> > Keep in mind that we support platforms without O_DSYNC. I am not
> > sure whether there are any that don't have O_SYNC either, but I am
> > fairly sure that we measured O_SYNC to be slower than fsync()s on
> > some platforms.

This measurement is quite understandable, since the current software
does 8k writes, and the OS only has a chance to write bigger blocks in the
write+fsync case. In the O_SYNC case you need to group bigger blocks yourself.
(bigger blocks are essential for max IO)

I am still convinced, that writing bigger blocks would allow the fastest
solution. But reading the recent posts the solution might only be to change
the current "loop foreach dirty 8k WAL buffer write 8k" to one or two large
write calls.

Andreas

Browse pgsql-hackers by date

  From Date Subject
Next Message Shridhar Daithankar 2002-10-07 09:37:29 Re: Large databases, performance
Previous Message Steve King 2002-10-07 08:02:04 Re: Bad rules