Clock with Adaptive Replacement
| От | Konstantin Knizhnik |
|---|---|
| Тема | Clock with Adaptive Replacement |
| Дата | |
| Msg-id | 56BCF6FD.3030602@postgrespro.ru обсуждение исходный текст |
| Ответы |
Re: Clock with Adaptive Replacement
Re: [HACKERS] Clock with Adaptive Replacement |
| Список | pgsql-hackers |
Hi hackers,
What do you think about improving cache replacement clock-sweep algorithm in PostgreSQL with adaptive version proposed
inthis article:
http://www-cs.stanford.edu/~sbansal/pubs/fast04.pdf
Are there some well known drawbacks of this approach or it will be interesting to adopt this algorithm to PostgreSQL
andmeasure it impact om performance under different workloads?
I find this ten years old thread:
http://www.postgresql.org/message-id/flat/d2jkde$6bg$1@sea.gmane.org#d2jkde$6bg$1@sea.gmane.org
but it mostly discus possible patent issues with another algorithm ARC (CAR is inspired by ARC, but it is different
algorithm).
As far as I know there are several problems with current clock-sweep algorithm in PostgreSQL, especially for very large
caches.
May be CAR can address some of them?
--
Konstantin Knizhnik
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
В списке pgsql-hackers по дате отправления: