Romex Software Forum

With a boot-time-load driver, I don't readily see any pitfalls except dealing with interrupted writes to files that are also boot-time loaded and do so before our driver (these are always in use and are typically replaced with PendingFileRenameOperations)... as well as of filesystem metadata related...

Was the key factor in me declaring the software "not ready for production use", too.

Currently, if I select a line pertaining to a cache task in the PrimoCache main window, no statistics are displayed.

Why not display cumulative statistics for all affected drives instead so I can readily see the overall caching effectiveness?

Monitoring the stats during defragmentation, I do see that the cached data appear to be invalidated: the amount of L2 cached data drops dramatically.

Do defragmenters have any adverse impact on PrimoCache - e.g. invalidate cache contents? I'm primarily concerned about L2.

View (manually) which files the cached blocks correspond to with the usage stats that the program itself uses. * view by files: ** list, optionally w/quick search/sorting ** for each, amount/percentage cached, aggregate usage stats * view by block: ** map with scaling, maybe like MyDefrag ** usage s...

Manually upload to SSD files/folders that I expect to be used extensively (e.g. databases).

Primarily intended for initial cache population to reduce the related performance hit.