Re: data on devel code perf dip

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, maryedie(at)osdl(dot)org, pgsql-hackers(at)postgresql(dot)org, Mark Wong <markw(at)osdl(dot)org>, Josh Berkus <josh(at)agliodbs(dot)com>
Subject: Re: data on devel code perf dip
Date: 2005-08-12 02:11:42
Message-ID: 200508120211.j7C2Bgb01740@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> >> O_DIRECT is only being used for WAL page writes (or I sure hope so
> >> anyway), so shared_buffers should be irrelevant.
>
> > Uh, O_DIRECT really just enables when open_sync is used, and I assume
> > that is not used for writing dirty buffers during a checkpoint.
>
> I double-checked that O_DIRECT is really just used for WAL, and only
> when the sync mode is open_sync or open_datasync. So it seems
> impossible that it affected a run with mode fdatasync. What seems the
> best theory at the moment is that the grouped-WAL-write part of the
> patch doesn't work so well as we thought.

Yes, that's my only guess. Let us know if you want the patch to test,
rather than pulling CVS before and after the patch was applied.

--
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

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2005-08-12 02:14:53 Re: Why do index access methods use LP_DELETE?
Previous Message Tom Lane 2005-08-12 02:09:19 Re: data on devel code perf dip

Browse pgsql-patches by date

  From Date Subject
Next Message William ZHANG 2005-08-12 02:20:32 Re: Bug in canonicalize_path()
Previous Message Tom Lane 2005-08-12 02:09:19 Re: data on devel code perf dip