PrimoCache flushes deleted data? Win Server 2022

[Axiomatic]

I'm trying to use Primo to accelerate a 4x 4TB HDD array (mirrored) with 2x 1TB Samsung 980 Pros (mirrored). I'm a video editor, so I regularly deal with single-file sizes on the order of many hundreds of GB. I fully utilize this cache regularly, and I also delete things often.

I just moved over a 600GB project file, noticed it was the wrong one, then deleted it. I then wanted to try different cache config settings bc I've been having strange performance issues. The second I changed the cache config, Primo insisted on flushing that 600GB of now-deleted project data to my spinners, and now I'm gonna be here for a while...

How can I avoid this in the future?

[Support]

To keep deleted files from being written to disk, the file system of the target volume needs to be NTFS, and you need to wait about 30 seconds for Windows to mark corresponding disk sectors deleted. You can view "Trimmed Blocks" in the cache task stats panel. This entry roughly represents the amount of write-data that is blocked from being written to disk.

For more information, please see
https://www.romexsoftware.com/en-us/pri ... -wear.html