Recommended Posts

Does anyone know what kind of changes MSFT did to superfetch? and I need alittle help understand how superfetch really works.. I know superfetch caches your well used programs so they start faster.. But at what point does it re-cache? When i install a new program? Could use alittle information.

Does anyone know what kind of changes MSFT did to superfetch? and I need alittle help understand how superfetch really works.. I know superfetch caches your well used programs so they start faster.. But at what point does it re-cache? When i install a new program? Could use alittle information.

I believe the system just learns you habbits a loads the most common files you used into the memory. When a application starts (lets say an application heavy on memory) it releases the memory to the application. When that application terminates, it then re-caches any commonly used data back into memory. I believe the system does everything automatically and doesn't "reset" itself every time an application gets installed.

I hope this helps.

Superfetch in Windows 7 is also a lot less aggressive than Vista's. On Vista I was often annoyed that it started caching almost immediately after logging in and just had to fill the entire available memory. (Edit - it also cached large files used by applications, like partial torrent downloads - W7 doesn't)

Windows 7 is a bit different - after logging in, I can see some amount of memory is already used for the cache, but the system waits a few minutes before really starting "superfetching". It also doesn't use all the available memory if there's no need to (not enough data to cache). Also, after quitting a program, refilling the cache doesn't occur immediately. It seems that the I/O priority is also lower.

Edited by soulburner
Which is a bad thing how? I mean if you had lets say, 12GB of ram via triple channel DDR3 on a i7 platform would you really have enough programs to have that filled?

Exactly, and if you had a slow hard drive then it would take time to fill that amount of memory up. Free RAM is wasted RAM, but no point in caching RAM with stuff you actually don't need.

FALSE! Superfetch doesn't fetch the users files but only the binaries exe and DLL libraries.

What was loading these files then, making my hard drive cry for help? It wasn't indexing, because this location has not been added to be indexed. If I recall correctly, it was svchost.exe with Background I/O priority.

edit - this guy seems to be complaining about the same thing: http://jaysonrowe.com/2009/01/05/thoughts-...fetch-in-vista/ - read the paragraphs above and below the second screenshot.

Does anyone know what kind of changes MSFT did to superfetch? and I need alittle help understand how superfetch really works.. I know superfetch caches your well used programs so they start faster.. But at what point does it re-cache? When i install a new program? Could use alittle information.

They made it a little less agressive at startup so it doesn't get in the way of a usable desktop. Once the system is idle for a few minutes, then superfetch kicks in and does it's magic.

Free RAM is wasted RAM, but no point in caching RAM with stuff you actually don't need.

:rolleyes: I know this, but with 2GB of RAM, Vista fills up the cache (1500MB for me) in less then 2 min and now all apps starts fast. On Win7 I have 500MB free, unused and wasted RAM. This is bad, not the way Vista does it. I'm now back with Vista, because of the superfetch bug under Win7.

:rolleyes: I know this, but with 2GB of RAM, Vista fills up the cache (1500MB for me) in less then 2 min and now all apps starts fast. On Win7 I have 500MB free, unused and wasted RAM. This is bad, not the way Vista does it. I'm now back with Vista, because of the superfetch bug under Win7.

It's not a bug, like it's been stated in this thread, Superfetch has been changed to reflect better system performance. The more and more applications you run, the more memory it will use. Don't be silly.

it's your poorly written antivirus.

I don't use an AV.

I know what I saw and what my disk went through. It cached utorrent downloads, huge Steam's GCF files and stuff like that. It really does stuff like this: http://jaysonrowe.files.wordpress.com/2009/01/superfetch.png

Windows 7's Superfetch is a huge improvement!

edit:

:rolleyes: I know this, but with 2GB of RAM, Vista fills up the cache (1500MB for me) in less then 2 min and now all apps starts fast. On Win7 I have 500MB free, unused and wasted RAM. This is bad, not the way Vista does it. I'm now back with Vista, because of the superfetch bug under Win7.

You do realize that Vista is caching junk (stuff you will probably never know Windows had) just to keep the Superfetch buffer full?

I don't use an AV.

I know what I saw and what my disk went through. It cached utorrent downloads, huge Steam's GCF files and stuff like that. It really does stuff like this: http://jaysonrowe.files.wordpress.com/2009/01/superfetch.png

Windows 7's Superfetch is a huge improvement!

Exactly, I'd rather have Superfetch cache applications and not every single file I might commonly use.

sorry, superfetch in Win7 makes Win7 slower, NOT faster!

Sorry, but have you given Windows 7 at least a few days to speed up? People complained about Vista and it's very aggressive way of using Superfetch because it cached literally everything. Windows 7 will take a little longer, but after a few reboots/days of using applications, Windows will learn and use Superfetch efficiently. But, if that doesn't work, I'm going to have a guess and say your problem is down to drivers or a bad install.

Yup, Windows 7's "standby" memory will increase when you launch more and more applications. After a fresh install, Superfetch uses a few hundred megabytes. After I installed and used applications like Adobe Photoshop, MSVC 2008 and others, I found the blue bar in Resource Manager covering the whole graph, leaving 0-50MB's truly free - just like Vista tries to do after the very first boot, only this time it's filled with program data that I actualy used.

And all apps I used start up much faster than on XP, which is a sign Superfetch does work just fine.

What was loading these files then, making my hard drive cry for help? It wasn't indexing, because this location has not been added to be indexed. If I recall correctly, it was svchost.exe with Background I/O priority.

aysonrowe.com/2009/01/05/thoughts-...fetch-in-vista/[/url] - read the paragraphs above and below the second screenshot.

That thing making your hard disk 'cry for help' is called a paging file, inevitably on systems with lower amounts of memory, things will get paged more often, and of course the actual fetching of your data into memory.

I don't use an AV.

I know what I saw and what my disk went through. It cached utorrent downloads, huge Steam's GCF files and stuff like that. It really does stuff like this: http://jaysonrowe.files.wordpress.com/2009/01/superfetch.png

Windows 7's Superfetch is a huge improvement!

That graph only shows what file the process is accessing, accessing data doesn't automatically mean it is loaded into memory. For the purpose of proof, I opened a large file with WinRar and extracted it to another folder to show the same effect.

post-286512-1244148011_thumb.jpg

That thing making your hard disk 'cry for help' is called a paging file, inevitably on systems with lower amounts of memory, things will get paged more often, and of course the actual fetching of your data into memory.

I don't think Vista uses the pagefile so intensively after starting up on a 3GB system. Also, when Vista is accessing data from the pagefile, the resource manager will show pagefile.sys under Disk as the file used.

That graph only shows what file the process is accessing, accessing data doesn't automatically mean it is loaded into memory. For the purpose of proof, I opened a large file with WinRar and extracted it to another folder to show the same effect.

Yes, I know, but whenever you see svchost.exe with a Background I/O priority - it's Superfetch.

The Resource Manager under Vista did not use bytes/second units - it used bytes per minute. When I saw "source 2007 materials.gcf" being read there and the "B/min" value was rising and rising and rising, I think it's fair to conclude it's actualy being read from the disk, and it was done so by svchost.exe with background IO - what other purpose of that than "superfetching" it? Oh, and the amount of free memory kept decreasing, so it wasn't just accessing the data, it was reading it into RAM.

Edited by soulburner
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • My father still uses a programme written in dbase3. Still manages to work with a little help from dosbox. 
    • Microsoft hides these secret Windows 11 performance boost settings available on every PC by Sayan Sen Windows enthusiasts often look for ways to extract as much performance out of their systems as possible, and it's often the case that they try and do so while trying to minimize the heat and power consumption. This is especially relevant in the case of mobile Windows PCs since laptops and notebooks tend to get hot and management of that heat and power is harder in such a form factor. As such users often turn to techniques like under-volting which can be used to squeeze out the maximum capabilities of a chip while also maintaining lowered power levels. There are official apps from AMD and Intel with the likes of Ryzen Master and XTU (Extreme Tuning Utility). While these are quite handy, most enthusiasts probably prefer to dig into the BIOS and play around with settings there like Curve Optimizer on Ryzen, which lets users set various frequency-voltage scaling values. These are essentially called P-States. If you are not familiar with them, Processor Power Management is done through Advanced Configuration and Power Interface (ACPI) P-states and C-states. While P-states or performance pwoer states handle CPU voltage-frequency scaling, C-states deal with CPU sleep states so that some of the CPU functions, which are not necessary at that moment, can be disabled. The P-states and C-states work together to make the processor run more efficiently. It helps the OS and apps determine which cores can be parked and which should be boosted. Of course not every user is an enthusiast or knows the technicalities and integrities of how things like overclocking or undervolting work. Thankfully for them Windows itself offers something pretty cool, though it is hidden by default on all systems. By default, Windows only has two P-States, "Minimum Processor State" and "Maximum Processor State." However, this can be changed with a Registry trick to expand the options under a secret "Processor performance boost mode" dropdown. This essentially enables the HWP or hardware P-States available on a device, and these are not controlled just by the OS itself as the underlying hardware gets involved too. In total there are five Processor Performance Boost Mode profiles that control how Windows requests and allows CPU turbo/boost behavior under the different power policies. They are: Disabled: In this mode, processor boosting is effectively turned off. The CPU will avoid entering turbo or boost frequencies and instead operate closer to its base frequency ceiling. This can significantly reduce power consumption and heat output, but at the cost of reduced burst performance and responsiveness in short workloads. Enabled: This is the standard behavior where boost functionality is allowed under normal conditions. The processor can opportunistically increase frequency when workload demands it, balancing performance gains with power and thermal constraints as managed by the system. Aggressive: Aggressive mode favors performance more heavily, allowing the CPU to enter higher boost states more readily and sustain them longer. This should in theory improve responsiveness under bursty or heavy workloads but increases power draw and thermal output compared to the default enabled behavior. Efficient Enabled: This mode still allows boosting, but with a stronger bias toward energy efficiency. The system attempts to use boost more selectively, avoiding unnecessary frequency spikes when the performance gain is marginal. Efficient Aggressive: This is a hybrid approach where boost is still performance-responsive, but the system continuously weighs efficiency more heavily than in Aggressive mode. It aims to deliver noticeable performance improvements while reducing wasted power in less demanding scenarios. Here's how to enable the Processor performance boost mode: Open Registry Editor: Press Win+R, type regedit, and click OK. Go to: HKLM\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\54533251-82be-4824-96c1-47b60b740d00\be337238-0d82-4146-a960-4f3749d470c7 (where HKLM stands for HKEY_LOCAL_MACHINE_) Modify the value of Attributes from 1 to 2 (you can find modify option by right-clicking) After that, exit Registry, you should now be able to see the new "Processor performance boost mode" dropdown menu: As you can see there are now five new P-States or CPPC states or power profile available that help define the boost mode processor setting on your PC. Wrapping it up here's a quick run-down of the settings as defined by Microsoft itself. Setting Description Disabled The corresponding P-state-based behaviour is disabled. Collaborative Processor Performance Control (CPPC) behaviour is disabled. Enabled The corresponding P-state-based behaviour is enabled. CPPC behaviour is Efficient Enabled. Aggressive The corresponding P-state-based behaviour is enabled. CPPC behaviour is Aggressive. Efficient Enabled The corresponding P-state-based behaviour is Efficient. CPPC behaviour is Efficient Enabled. Efficient Aggressive The corresponding P-state-based behaviour is Efficient. CPPC behaviour is Aggressive. Aggressive At Guaranteed Windows calculates the desired extra performance above the guaranteed performance level, and asks the processor to deliver that specific performance level. Efficient Aggressive At Guaranteed Windows always asks the processor to deliver the highest possible performance above the guaranteed performance level. In the next part we shall be comparing these settings to explore how much of a benefit or regression they can provide in terms of performance and power efficiency. If you decide to change the values on your system and are experiencing problems like crashes or an overheating PC, make sure to revert the steps back to the original state.
    • I think he means you haven't reviewed previous UFC games. Of course it doesn't matter... Every time you just report on something that involves the President even if just simply what happened you guys usually get accused of being anti-Trump. We live in fun times.
  • Recent Achievements

    • One Month Later
      Leroy Jethro Gibbs earned a badge
      One Month Later
    • Conversation Starter
      flexorcist earned a badge
      Conversation Starter
    • One Month Later
      AndreaB earned a badge
      One Month Later
    • One Month Later
      agatameier earned a badge
      One Month Later
    • Week One Done
      agatameier earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      518
    2. 2
      +Edouard
      198
    3. 3
      PsYcHoKiLLa
      147
    4. 4
      ATLien_0
      93
    5. 5
      Steven P.
      77
  • Tell a friend

    Love Neowin? Tell a friend!