Re: Move unused buffers to freelist - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Move unused buffers to freelist
Date
Msg-id CA+U5nMK+kGz8FM-oDepsYszd6xTiF9ghEJvsE1G41cg_HaA6DQ@mail.gmail.com
Whole thread Raw
In response to Re: Move unused buffers to freelist  (Greg Smith <greg@2ndQuadrant.com>)
Responses Re: Move unused buffers to freelist
List pgsql-hackers
On 3 July 2013 12:56, Amit Kapila <amit.kapila@huawei.com> wrote:
 
>My perspectives here would be

> * BufFreelistLock is a huge issue. Finding a next victim block needs to be
an O(1) operation, yet it is currently much worse than that. Measuring
> contention on that lock hides that problem, since having shared buffers
lock up for 100ms or more but only occasionally is a huge problem, even if
it
> doesn't occur frequently enough for the averaged contention to show as an
issue.

  To optimize finding next victim buffer, I am planning to run the clock
sweep in background. Apart from that do you have any idea to make it closer
to O(1)?

Yes, I already posted patches to attentuate the search time. Please check back last few CFs of 9.3
 
--
 Simon Riggs                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: Move unused buffers to freelist
Next
From: Amit Kapila
Date:
Subject: Re: Review: Patch to compute Max LSN of Data Pages