Re: The shared buffers challenge - Mailing list pgsql-performance

From Merlin Moncure
Subject Re: The shared buffers challenge
Date
Msg-id BANLkTimu7NWGziDqHWE8CXkWR11ahPVw9g@mail.gmail.com
Whole thread Raw
In response to Re: The shared buffers challenge  (Jeff Davis <pgsql@j-davis.com>)
List pgsql-performance
On Fri, May 27, 2011 at 7:19 PM, Jeff Davis <pgsql@j-davis.com> wrote:
> On Thu, 2011-05-26 at 09:31 -0500, Merlin Moncure wrote:
>> Where they are most helpful is for masking of i/o if
>> a page gets dirtied >1 times before it's written out to the heap
>
> Another possible benefit of higher shared_buffers is that it may reduce
> WAL flushes. A page cannot be evicted from shared_buffers until the WAL
> has been flushed up to the page's LSN ("WAL before data"); so if there
> is memory pressure to evict dirty buffers, it may cause extra WAL
> flushes.
>
> I'm not sure what the practical effects of this are, however, but it
> might be an interesting thing to test.

Hm, I bet it could make a fairly big difference if wal data is not on
a separate volume.

merlin

pgsql-performance by date:

Previous
From: Grzegorz Jaśkiewicz
Date:
Subject: Re: Delete performance
Next
From: Jenish
Date:
Subject: Strange behavior of child table.