![]() If the 500MB file was loaded with the intention of hashing or encrypting it then there would be no need for it to be cached unlike an exe or dll which may get opened and closed several times during a Windows session such as a web browser or email client or even a compiler and there respective components. We could use my ClearFileCache in the above link but the damage has already been done and that function was written to provide a level playing field for code testing purposes. It may take sometime before any of the 500MB file gets moved out. That went into the filecache so, obviously, something else got its marching orders. I then opened a photo editor which I knew was not in the filecache. Obviously I hit the 'wall' and 0.4GB of the filecache was dumped with extreme prejudice. I opened a 500MB file which was not cached and saw the cached figure increase to 5.6GB. In Windows 10 Task Manager I have 2.4GB of RAM in use and 5.5GB cached totaling 7.9GB from the 8GB I have on board. This thread has spawned from Faster file loading
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |