Comments on: Nutanix Acropolis Operating System Compression and Deduplication https://magander.se/nutanix-acropolis-operating-system-compression-and-deduplication/ Fri, 19 Oct 2018 17:34:53 +0000 hourly 1 https://wordpress.org/?v=6.9.4 By: David Hocking https://magander.se/nutanix-acropolis-operating-system-compression-and-deduplication/#comment-62498 Mon, 04 Jan 2016 14:12:02 +0000 http://magander.se/?p=6434#comment-62498 In reply to magander3.

Thanks, just out of interest, given that the dedupe process is metadata only, do you know why it goes into the single touch pool in the first place?

]]> By: magander3 https://magander.se/nutanix-acropolis-operating-system-compression-and-deduplication/#comment-62495 Mon, 04 Jan 2016 13:36:01 +0000 http://magander.se/?p=6434#comment-62495 In reply to David Hocking.

Hi David,
it does nit stay in the cache forever. It gets pulled into a section called Single Touch pool (backed by RAM only) and if touched again it will placed in the Multi Touch section of the content cache which is backed by both RAM and SSD. Both single and Multi Touch sections uses LRU to evict data from the cache.

//Magnus

]]> By: David Hocking https://magander.se/nutanix-acropolis-operating-system-compression-and-deduplication/#comment-62492 Mon, 04 Jan 2016 13:20:48 +0000 http://magander.se/?p=6434#comment-62492 In the article, it states…
“Deduplicated data is pulled into the content cache (backed by RAM and SSD) using 4KB block size”

..how long does it stay there? – i.e. does it become a “hot” and just stay there for good, or does it just fall into the LRU cycle and get evicted as normal?

]]>