lru cache replacement

From: xoror(at)infuse(dot)org
To: pgsql-hackers(at)postgresql(dot)org
Cc: yutaka(at)nonsensecorner(dot)com, pgman(at)candle(dot)pha(dot)pa(dot)us
Subject: lru cache replacement
Date: 2003-06-24 10:13:51
Message-ID: Pine.GSO.4.10.10306241207020.6091-100000@taurus
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I was researching on cache replacement strategy as well. 2Q has one
disadvantage see this exellent paper:
http://www.almaden.ibm.com/cs/people/dmodha/#ARC see the paper
"ARC: A Self-Tuning, Low Overhead Replacement Cache" for theory and "One
Up on LRU" for implementation details. ARC requires no tuning and can
switch fast between chaging patterns. Best of all is it is resistant to a
"sequential scan" pattern. and i think it's even easier to implement then
2q :)

does pgbench test with relatively large sequential scans?

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andreas Pflug 2003-06-24 10:38:40 Re: pg_get_triggerdef in pg_dump
Previous Message Ronald Khoo 2003-06-24 08:49:17 2PC: discussion in comp.arch