NOTICE: Registration may require manual admin activation. After registering visit https://bitsum.com/contact/ to request account activation.
Started by BenYeeHua, May 22, 2013, 05:52:18 PM
QuoteWhenever memory becomes free-for example, when an application exits or releases memory-SuperFetch asks the Memory Manager to fetch data and code that was recently evicted. This is done at a rate of a few pages per second with Very Low priority I/Os so that the preloading does not impact the user or other active applications. Therefore, if you leave your computer to go to lunch and a memory-intensive background task causes the code and data from your active applications to be evicted from memory while you're gone, SuperFetch can often bring all or most of it back into memory before you return. SuperFetch also includes specific scenario support for hibernation, standby, Fast User Switching (FUS), and application launch. When the system hibernates, for example, SuperFetch stores data and code in the hibernation file that it expects (based on previous hibernations) will be accessed during the subsequent resume. In contrast, when you resume Windows XP, previously cached data must be reread from the disk when it is referenced.
QuoteWe also compared the startup performance of a couple of applications, including Outlook 2010 Beta, which needed five seconds longer to start and navigating between folders felt sluggish. Launching even the very slim Google Chrome browser took about seven seconds, whereas the original test only took four seconds. This is not good.
Quote from: edkiefer on May 27, 2013, 01:00:12 PMAccording to that link i posted to win7 , page 202 superfetch gets disabled on very fast HD (SSD's ) , 6.5 in WEI .It tells you how to set superfetch in registry , there 3 options 0-3 values for superfetch and prefetcher .
Quote from: Support on May 29, 2013, 02:23:58 PMYes, it does say that! I expected ReadyBoost to be disabled, but I did not expect SuperFetch to be disabled. It does make sense, given that the primary purpose is to speed up hard disk I/O. I still believe users will, generally speaking, do more harm than good by adjusting its state though.
QuoteSuperFetch and prefetch are storage management technologies in Windows that provide a fast-track access to data on traditional, slower hard drives. On SSD drives these really clever services only provide for unnecessary write operations. Typically, Windows 7 automatically disables these services for your SSD disk. Otherwise disable it manually.
Quote from: chris635 on April 30, 2016, 11:27:47 AMUnder readyboot properties click file and check circular. The error goes away with this too.
Quote from: chris635 on April 30, 2016, 11:39:23 AMI have been running readyboot like this for several years now, and I have never seen it get bigger, and with no side effects. It tracks only the most recent file changes from what I have read in the past with circular checked.
Quote from: chris635 on April 30, 2016, 12:42:13 PMI have an SSD. Superfetch is running and set to automatic, but windows deletes the superfetch key.
Quote from: Jeremy Collake on April 30, 2016, 01:05:39 PMI am not up to speed on the changes Microsoft made to SuperFetch after NT6. I think everyone sees the days where all systems have enough RAM, and an SSD, so that this type of 'history based pre-fetching' is not necessary.
Quote from: chris635 on April 30, 2016, 01:51:15 PMWhen I was on win7, yes it kept those keys, just disabled the service. I believe it changed with win8.
Quote from: edkiefer on September 09, 2016, 03:58:11 PMI forgot to update this post with new Win10 and AU (1607 build), as Chris mentioned early, MS now has superfetch key gone and the readyboot folder in windows is empty now, so only prefetcher reg key is 3
Quote/prefetch:# arguments to use when launching various process types. It has been observed that when file reads are consistent for 3 process launches with the same /prefetch:# argument, the Windows prefetcher starts issuing reads in batch at process launch. Because reads depend on the process type, the prefetcher wouldn't be able to observe consistent reads if no /prefetch:# arguments were used. Note that the browser process has no /prefetch:# argument; as such all other processes must have one in order to avoid polluting its profile. Note: # must always be in [1, 8]; otherwise it is ignored by the Windows prefetcher. â†ª