the raw data could always be converted to a watchable file version...
or may be just display used file (write/read) according to cache...
we could some how access this suggestion with some task managing softs that displayed accessed r/w files...
Some Suggestions...
Re: Some Suggestions...
we really need an exclude option so defrag and antivirus software doesn't use up the cache also a smarter cache that remembers history i don't like the gamers mode idea caching data twice doesn't seem like a good use for ram also is anyone else getting filesystem minor errors with deferred write enabled??
Re: Some Suggestions...
@sparkler
That's why Virtual-block caching (aka FS-Level caching) is more efficient in these cases.. Defragmentation & some AV software manage data caching at the file level to optimize disk I/O & minimize cache thrashing by not using OS's file cache if necessary, through (e.g. FILE_FLAG_NO_BUFFERING, FILE_FLAG_WRITE_THROUGH, flags).. but can't do the same with FancyCache (Logical-block caching)..
BTW, it's better to keep defer write latency & cache size as small as possible, & [Release after write] option will help a lot as well..
That's why Virtual-block caching (aka FS-Level caching) is more efficient in these cases.. Defragmentation & some AV software manage data caching at the file level to optimize disk I/O & minimize cache thrashing by not using OS's file cache if necessary, through (e.g. FILE_FLAG_NO_BUFFERING, FILE_FLAG_WRITE_THROUGH, flags).. but can't do the same with FancyCache (Logical-block caching)..
BTW, it's better to keep defer write latency & cache size as small as possible, & [Release after write] option will help a lot as well..