Re: patch: improve SLRU replacement algorithm
От | Greg Stark |
---|---|
Тема | Re: patch: improve SLRU replacement algorithm |
Дата | |
Msg-id | CAM-w4HM76yi=Y-5Qtw_0iV5SeAVeGbA_XGL1dKC9Xoo1R1exQw@mail.gmail.com обсуждение исходный текст |
Ответ на | patch: improve SLRU replacement algorithm (Robert Haas <robertmhaas@gmail.com>) |
Ответы |
Re: patch: improve SLRU replacement algorithm
Re: patch: improve SLRU replacement algorithm |
Список | 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 по дате отправления: