From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Ants Aasma <ants(at)cybertec(dot)at> |
Cc: | Atri Sharma <atri(dot)jiit(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila(at)huawei(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Page replacement algorithm in buffer cache |
Date: | 2013-03-22 14:02:39 |
Message-ID: | 3985.1363960959@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Ants Aasma <ants(at)cybertec(dot)at> writes:
> You might want to check out the LIRS cache replacement algorithm [1].
> That algorithm tries to estimate least frequently used instead of
> least recently used. Mysql uses it for their buffer replacement
> policy. There is also a clock sweep based approximation called
> CLOCK-Pro. Papers describing and evaluating both are available on the
> net. The evaluations in the papers showed significantly better
> performance for both of those compared to regular clock sweep or even
> ARC.
I seem to recall that CLOCK-Pro, or something named similarly to that,
was one of the alternatives discussed when we went over to the current
clock-sweep approach. And we definitely looked at ARC. It might be
worth checking the archives from back then to see what's already been
considered.
> However, I think the main issue isn't finding new algorithms that are
> better in some specific circumstances. The hard part is figuring out
> whether their performance is better in general.
Yeah. You can prove almost anything with the right set of test cases :-(
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2013-03-22 14:02:45 | Re: Proposal for Allow postgresql.conf values to be changed via SQL [review] |
Previous Message | Atri Sharma | 2013-03-22 13:59:31 | Re: Page replacement algorithm in buffer cache |