( Is this post really as long winded as it seems? lol) So yeah the guys above who had huge caches will see very high benchmark numbers because as far as CrystalDisk is concerned, the transfer is complete as soon as the file is copied to RAM, not when it's written to disk. Try again using an 8GB cache and you'll see lightning fast (reported) transfer times. That's why your transfer times seemed slow, because they were. Once that happens all data in RAM must be written to the HDD (buffer flushing), before new data can be copied to RAM. RAM simply acts as a buffer, so data is first copied to the 512MB of RAM u reserved, while simultaneously writing from RAM to the HDD.īut data is copied to RAM faster than it can be written from RAM to the HDD so it takes only a few seconds for the 512MB RAM to fill up. For the sake of simplicity your 512MB cache will now be called RAM: But from my (professional) experience, it's very hard to notice any improvement except for specific situations (which I haven't found yet really ).Ĭlick to expand.Yeah because you were writing 4.5GB to a disk with only 512Mb of cache. I'm just kidding, I'm very interested about this topic. Please show us a screenshot of a 10GB copying action over those drives at 99% completion When you copy a very large file from G- to C-drive, at what speed does the action end? The file still needs to be copied to the slower HDD, so I reckon the speed rate will fall dramatically at the end of the copying action (or at shutdown or other checkpoints). In the background probably.Ībout the writes. Shutdows will be slower as the data has to be written to the HDD and startups will be slower due to starting caching the data from the disk.
#Fancycache download software#
PrimoCache probably does the same thing by software in RAM. A 40GB SSD cache drive using Intel Smart Response Technology will cache the most accessed data 'more permanently' (but a lot slower). But the improved reads will only shine when the data to be fetched has been cached already.
0 kommentar(er)
