Re: fsync method checking - Mailing list pgsql-hackers

From Zeugswetter Andreas SB SD
Subject Re: fsync method checking
Date
Msg-id 46C15C39FEB2C44BA555E356FBCD6FA40184CF68@m0114.s-mxs.net
Whole thread Raw
In response to fsync method checking  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: fsync method checking  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
> 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

Attachment

pgsql-hackers by date:

Previous
From: "Thomas Hallgren"
Date:
Subject: Re: pljava revisited
Next
From: Tom Lane
Date:
Subject: Re: Use of 'cp -r' in CREATE DATABASE