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

From Alvaro Herrera
Subject Re: patch: improve SLRU replacement algorithm
Date
Msg-id 1333560275-sup-4842@alvh.no-ip.org
Whole thread Raw
In response to Re: patch: improve SLRU replacement algorithm  (Greg Stark <stark@mit.edu>)
Responses Re: patch: improve SLRU replacement algorithm  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
Excerpts from Greg Stark's message of mié abr 04 14:11:29 -0300 2012:
> 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.

What this statement means to me is that the number of slru buffers
should be configurable, not compile-time fixed.

--
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support


pgsql-hackers by date:

Previous
From: Greg Stark
Date:
Subject: Re: patch: improve SLRU replacement algorithm
Next
From: Kyotaro HORIGUCHI
Date:
Subject: Re: Speed dblink using alternate libpq tuple storage