Re: patch: improve SLRU replacement algorithm - Mailing list pgsql-hackers

From Greg Stark
Subject Re: patch: improve SLRU replacement algorithm
Date
Msg-id CAM-w4HM76yi=Y-5Qtw_0iV5SeAVeGbA_XGL1dKC9Xoo1R1exQw@mail.gmail.com
Whole thread Raw
In response to patch: improve SLRU replacement algorithm  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: patch: improve SLRU replacement algorithm
Re: patch: improve SLRU replacement algorithm
List pgsql-hackers
On Wed, Apr 4, 2012 at 1:00 PM, Robert Haas <robertmhaas@gmail.com> wrote:
> , everybody's next few CLOG requests hit some other
> buffer but eventually the long-I/O-in-progress buffer again becomes
> least recently used and the next CLOG eviction causes a second backend
> to begin waiting for that buffer.

This still sounds like evidence that the slru is just too small for
this transaction rate. Otherwise there would be some other buffer that
would be accessed similarly infrequently.

Your fix sounds right to me but I would hope it should be fixing
something that would only happen rarely, not every time theres a
write. It sounds like the slru is thrashing quite a bit more than the
code anticipates.

-- 
greg


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: log chunking broken with large queries under load
Next
From: Tom Lane
Date:
Subject: Re: log chunking broken with large queries under load