Re: Changing the default wal_sync_method to open_sync for Win32?

From: Kenneth Marshall <ktm(at)it(dot)is(dot)rice(dot)edu>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Changing the default wal_sync_method to open_sync for Win32?
Date: 2005-03-17 14:12:58
Message-ID: 20050317141258.GA13019@it.is.rice.edu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-hackers-win32

On Wed, Mar 16, 2005 at 11:20:12PM -0500, Bruce Momjian wrote:
>
> Basically we do open_datasync -> fdatasync -> fsync. This is
> empirically what we found to be fastest on most operating systems, and
> we default to the first one that exists on the operating system.
>
> Notice we never default to open_sync. However, on Win32, Magnus got a
> 60% speedup by using open_sync, implemented using
> FILE_FLAG_WRITE_THROUGH. Now, because this the fastest on Win32, I
> think we should default to open_sync on Win32. The attached patch
> implements this.
>
> 2. Another question is what to do with 8.0.X? Do we backpatch this for
> Win32 performance? Can we test it enough to know it will work well?
> 8.0.2 is going to have a more rigorous testing cycle because of the
> buffer manager changes.
>
My preference would be to back-patch to 8.0.1. I have some projects
where the performance difference will decide whether or not they go
with MSSQL or PostgreSQL.

Ken

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2005-03-17 14:54:20 Re: PHP stuff
Previous Message Thomas Hallgren 2005-03-17 12:15:57 Re: Savepoints and SPI

Browse pgsql-hackers-win32 by date

  From Date Subject
Next Message Bruce Momjian 2005-03-17 17:30:37 Re: Changing the default wal_sync_method to open_sync for
Previous Message Merlin Moncure 2005-03-17 13:19:19 Re: Changing the default wal_sync_method to open_sync for Win32?