Anti-caching is _literally_ caching. The system may be fantastic, but that's what it's doing. Consider the following key characteristics of "anti-caching": (1

Anti-caching is _literally_ caching. The system may be fantastic, but that's what it's doing. Consider the following key characteristics of "anti-caching": (1) Cold data is moved from RAM to disk. This is cache replacement. Eventually, caches fill and you have to choose what to evict. While there are many replacement algorithms, one of the most popular is LRU, which is what is used here. In conventional CPU caches, data is moved a cache line at a time, moved transactionally. Here, it is a tuple at a time, moved transactionally. (2) There is only one item present in either RAM or disk. This is (almost) exclusive caching, which maintains exactly one item in all levels of the cache hierarchy (as done by the AMD Athlon). The key difference is removing it from the bottom of the hierarchy. This approach may be novel, but as far as I can tell, it is the primary novelty. To be clear, adapting all of this to DBMS architecture may be a great idea, but let's call things by their names.