L2 cache removal strategy?

[cichy45]

Hello all.

I use Primocache for many years now, but what I think it is missing is ability to select L2 removal strategy. I often encounter one single issue.

Lets say I have 120 GB cache SSD. I play game that uses 30 GB of that cache. Then I copy new files on the disk, but the files take ~60 GB.

Instead of removing from L2 cache the oldest, least used block, the new files take place of the most recently used (cached game files) and when I run game again it must be cached again.

What I would love to see is some type of Least Recently Used block discard strategy, (or Least Frequently Used (LFU)) so the newly cached files would replace the oldest, least used cache blocks instead of the most recently used blocks.
At this time, the current algorithm in my experience works like Last In, First Out (LIFO) or Most Recently Used (MRU), so the newest / most used blocks are discarded first, when cache is full.

Thanks!

[Support]

Actually, PrimoCache utilizes an optimized LRU (Least Recently Used) eviction algorithm for read caching, not LIFO (Last In First Out).