Re: patch: improve SLRU replacement algorithm
От | Alvaro Herrera |
---|---|
Тема | Re: patch: improve SLRU replacement algorithm |
Дата | |
Msg-id | 1333560275-sup-4842@alvh.no-ip.org обсуждение исходный текст |
Ответ на | Re: patch: improve SLRU replacement algorithm (Greg Stark <stark@mit.edu>) |
Ответы |
Re: patch: improve SLRU replacement algorithm
|
Список | 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 по дате отправления: