Should I disable Superfetch?

I know this thread has been inactive for some time, but I was looking for something and came across this and thought I would add my little bit of knowledge to the information. It might be useful. It might be interesting. It might not. Enjoy anyway.

leaving SuperFetch aside, which is an operating system service, when an application or data is loaded into memory, it takes up a certain amount of disk I/O time. To alleviate this problem, the system operates a caching operation. This is controlled by a function simply called caching. The system operates read-ahead caching and tries to pre-empt the data to be loaded (how it does this is the subject of a different discussion) and write-behind caching, where it keeps the data in memory for a certain period of time before actually writing it to the hard disk, whether this is a HDD or SSD, is not relevant.
The advantage of keeping applications in memory during a single boot, is that if you exit and then reload an application, it does not need to access the disk anywhere near as much. If you watch the disk activity light, you will see only a slight flicker if it is already is system cache.
The downside is the write-behind caching. If by chance your system crashes a moment after you have saved your data to disk, there is a possibility that it will not have actually been written to disk and is actually being held in this write behind cache and could be lost.
Windows does load managers for this process to make sure that any data not accessed for a short time is properly written to disk and to analyse active data, to assess when it can be written to disk without any detriment to the speed of access for the user. The process created for this purpose is called a lazy-writer and one is loaded every second to monitor what it going on.

There are two aspects to this. firstly, a lot of windows programs operate an auto save function, so you may have an ability to recover some of the lost data through the application auto save function. Secondly, the write-behind function can be disabled in the properties of the disk in device manager.
Unless you have a particularly slow system, disabling write-behind caching will not affect you in any noticeable way.

StephenAE said:

I know this thread has been inactive for some time, but I was looking for something and came across this and thought I would add my little bit of knowledge to the information. It might be useful. It might be interesting. It might not. Enjoy anyway..

Thanks, but NONE of your post relates to how superfetch works at all though does it? SuperFetch is the point of this thread. It is like you decided to start writing about disk cache and then forgot and wrote about autosave instead.

But thanks for the long story, I enjoyed it, and welcome :)

Perhaps it would be better to start a thread on your own subject next time.