PrimoCache performance and many one time writes
Posted: Mon Aug 20, 2018 12:36 pm
My system disk is monitored by PrimoCache.
On that disk is a certain folder that has very high number of one time writes. And a lesser number of one time reads.
Is it beneficial to move that folder to a disk that's not monitored by PrimoCache?
I ask because I see two possible dangers:
1] No matter how high the quality of the PrimoCache programming is, monitoring useless activity is still wasting CPU cycles.
2] It may flush out other blocks from the cache.
Number 2 may require extra information. That folder is constantly filled with little blocks incoming data and glued to what's allready there. If done it's moved out of that folder. The same data never returns.
On an SSD there is something like wear leveling so data after that likely is written on different sectors (if the disk isn't nearly full).
Not sure how a HDD handles it. Anyway my thought/fear is that PrimoCache gets tricked into thinking the sectors 'in' that folder are extremely busy, so very worthwhile caching them. But in reality they are the most useless of the whole disk, because they only exist between 0-60 seconds...
On that disk is a certain folder that has very high number of one time writes. And a lesser number of one time reads.
Is it beneficial to move that folder to a disk that's not monitored by PrimoCache?
I ask because I see two possible dangers:
1] No matter how high the quality of the PrimoCache programming is, monitoring useless activity is still wasting CPU cycles.
2] It may flush out other blocks from the cache.
Number 2 may require extra information. That folder is constantly filled with little blocks incoming data and glued to what's allready there. If done it's moved out of that folder. The same data never returns.
On an SSD there is something like wear leveling so data after that likely is written on different sectors (if the disk isn't nearly full).
Not sure how a HDD handles it. Anyway my thought/fear is that PrimoCache gets tricked into thinking the sectors 'in' that folder are extremely busy, so very worthwhile caching them. But in reality they are the most useless of the whole disk, because they only exist between 0-60 seconds...