Proceedings of the 4th International Symposium on Memory Management 2004
DOI: 10.1145/1029873.1029887
|View full text |Cite
|
Sign up to set email alerts
|

General adaptive replacement policies

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1

Citation Types

0
3
0

Year Published

2006
2006
2018
2018

Publication Types

Select...
6
1
1

Relationship

0
8

Authors

Journals

citations
Cited by 11 publications
(3 citation statements)
references
References 18 publications
0
3
0
Order By: Relevance
“…LRFU [5] is the novel caching algorithms that have attempted to combine recency and frequency (CRF) with the intent of removing one or more disadvantages of LRU. The police always choose a block with minimum value of CRF to evict.…”
Section: Related Workmentioning
confidence: 99%
“…LRFU [5] is the novel caching algorithms that have attempted to combine recency and frequency (CRF) with the intent of removing one or more disadvantages of LRU. The police always choose a block with minimum value of CRF to evict.…”
Section: Related Workmentioning
confidence: 99%
“…They prove robustness of EELRU with respect to LRU. They call a policy A robust with respect to policy B if A is k-miss-competitive relative to B for some k. In subsequent work (Smaragdakis 2004) shows how to construct a policy AB from two given policies A, B, that is 2-robust, i.e. 2-miss-competitive, with respect to both A and B.…”
Section: Related Workmentioning
confidence: 99%
“…The problem is very similar to the block replacement in cache memories except that it may argued that the page replacement is more critical as page transfers from disk to memory are orders of magnitudes slower than block transfers from main memory to the cache memory. Many page replacement algorithms [1,[4][5][6][7][8] exist including but not limited to the Not Recently Used (NRU), Second Chance, First In First Out (FIFO), Least Recently Used (LRU), Optimal, and Aging. Good replacement can reduce the page fault cost resulting in higher performance, since the more page faults the operating system encounters, the more resources are wasted on paging in/out instead of doing useful work, resulting ultimately in serious thrashing problems.…”
Section: Introductionmentioning
confidence: 99%