From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: fsync method checking |
Date: | 2004-03-18 18:40:43 |
Message-ID: | 200403181840.i2IIeh309334@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-performance |
Andrew Dunstan wrote:
>
>
> Bruce Momjian wrote:
>
> >I have been poking around with our fsync default options to see if I can
> >improve them. One issue is that we never default to O_SYNC, but default
> >to O_DSYNC if it exists, which seems strange.
> >
> >What I did was to beef up my test program and get it into CVS for folks
> >to run. What I found was that different operating systems have
> >different optimal defaults. On BSD/OS and FreeBSD, fdatasync/fsync was
> >better, but on Linux, O_DSYNC/O_SYNC was faster.
> >
> >[snip]
> >
> >Linux 2.4.9:
> >
> >
>
> This is a pretty old kernel (I am writing from a machine running 2.4.22)
>
> Maybe before we do this for Linux testing on a more modern kernel might
> be wise.
Sure, I am sure someone will post results.
--
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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-03-18 18:44:02 | Re: [HACKERS] fsync method checking |
Previous Message | Josh Berkus | 2004-03-18 18:32:43 | Re: COPY formatting |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-03-18 18:44:02 | Re: [HACKERS] fsync method checking |
Previous Message | Andrew Dunstan | 2004-03-18 18:23:14 | Re: fsync method checking |