Currently, cache_mover will move files from cache to the disk pool when cache usage is over the configured threshold.
This is fine, but some use cases may result in not hitting the threshold for a long time, in turn resulting in data sitting in cache for a long time.
For example, I've not written much to my storage for a few weeks, but Frigate is constantly writing a rolling ~180GB of data. This results in ~20% usage on my cache disk, so none of this is never moved to the pool.
An age threshold that acts secondarily to the utilisation threshold would be useful for such cases. This logic could be disabled in config with e.g. AGE_THRESHOLD: 0.
Not a huge priority for me so no rush, and I'll likely get round to implementing this myself if you don't have time as IIRC I had some other tweaks I was planning to PR as well.
Currently, cache_mover will move files from cache to the disk pool when cache usage is over the configured threshold.
This is fine, but some use cases may result in not hitting the threshold for a long time, in turn resulting in data sitting in cache for a long time.
For example, I've not written much to my storage for a few weeks, but Frigate is constantly writing a rolling ~180GB of data. This results in ~20% usage on my cache disk, so none of this is never moved to the pool.
An age threshold that acts secondarily to the utilisation threshold would be useful for such cases. This logic could be disabled in config with e.g.
AGE_THRESHOLD: 0.Not a huge priority for me so no rush, and I'll likely get round to implementing this myself if you don't have time as IIRC I had some other tweaks I was planning to PR as well.