In theory, Superfetch seems like a good idea, but could it suffer from a bit of insanity? I've noticed, that when I've used a virtual machine (in VMWare) and shut down the virtual machine, the HDD LED lights up for 5-10 minutes and the HDD noise is a major nuisance. Looking in resource monitor, it seems that Vista keeps reading the virtual disk file of the VM I've just shut down. Stopping Superfetch stops the HDD noise.
Why would Superfetch start caching a VM disk file when I've shut down the VM? Isn't the whole point of Superfetch to cache files before I use them, and not when I've finished using them?
Also, when I start the system, the HDD works constantly the first 20-30 minutes. I've got 8 GB RAM, and reading 8 GB from the disk doesn't take 20 minutes, so how can Superfetch spend so much time reading the disk when it should have filled all the available cache memory within 10 minutes of frantic HDD reading?
Why would Superfetch start caching a VM disk file when I've shut down the VM? Isn't the whole point of Superfetch to cache files before I use them, and not when I've finished using them?
Also, when I start the system, the HDD works constantly the first 20-30 minutes. I've got 8 GB RAM, and reading 8 GB from the disk doesn't take 20 minutes, so how can Superfetch spend so much time reading the disk when it should have filled all the available cache memory within 10 minutes of frantic HDD reading?