| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Greg Stark <stark(at)mit(dot)edu> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: patch: improve SLRU replacement algorithm |
| Date: | 2012-04-04 17:25:11 |
| Message-ID: | 1333560275-sup-4842@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)gmail(dot)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(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kyotaro HORIGUCHI | 2012-04-04 17:28:41 | Re: Speed dblink using alternate libpq tuple storage |
| Previous Message | Greg Stark | 2012-04-04 17:19:29 | Re: patch: improve SLRU replacement algorithm |