Detailed vista/win7 memory management

Detailed vista/win7 memory management, for Windows Vista, Windows7 memory usage, most users who upgrade from XP think: The System idle memory should be more and better. By the time of 7 (and more accurately vista), the idea that this should be changed is still lingering in everyone's memory. So here Windows7 new memory management mechanism "Superfetch" introduced to everybody, let everybody understand Windows7 memory occupy big reason.

What is the difference between Windows 7 memory management

"Superfetch" is not a new technology that has been introduced in the Vista era, but given the relatively small number of people using Vista and the various computer skills of the XP era, many are wondering why Windows7 memory footprint is so great.

The SuperFetch memory management mechanism can preload the application pages that the user may use using memory free space, avoid the system from the hard disk's page calls as much as possible, let the application run at the fastest speed, and do not slow down the sudden use because the computer is idle for a long time; When you exit a large application, you are proactively transferring the pages that were previously forced into virtual memory into memory. This may seem like a professional point, so looking down, it's a good way to understand these characteristics.

Why is it slow to start the program the first time?

I believe we all have had similar experiences. When I boot up, run a program for the first time, such as word, it may take 5 seconds to start. When I turn it off, it may take only 2 seconds. If I don't close, open another Word file directly, that's faster.

What is the cause of this?

When we boot up, the working set does not have Word this employee (page), he is still at home (hard disk) inside. So when I called him, it came from home to the Office (working set). This process is called a hard paging, of course, takes a long time. And when we closed word, he was sent to another room in the building, but I immediately summoned him again, at this time, the data in the other room has not been cleared, he does not have to come from home, but directly from the data structure to introduce it. Without closing the program word, he doesn't have to give way to other programs, it still exists in the office (working set), and it's quicker to call him. The process of "no need to recall data from the hard disk, but to mount the page in the data structure back to the work set" is called soft paging. We all know that the memory speed is much faster than the hard disk, so the use of "soft paging" is the second run of the program has become very fast reason.

The reason Windows 7 memory footprint is large

Now we know that when there is a need for a program page in memory, the program can be started faster. And Windows7 in the "Superfetch" already has the function of learning, since the first use of Windows7, Superfetch began to record our use habits, we often use the program's page after the boot to load, Then we can get the same speed as the second time when we open the program for the first time. So these preloaded pages will make our memory footprint much more. Simply put, all program operations in memory, to avoid using hard disk hard paging space, which is why feel Windows7 occupy a lot of memory reasons.

View pre-loaded memory

And in the XP era, you might have had a similar experience: when you started using some programs, you left because of something. Back to find the system response is very slow, particularly bad. This is because XP's memory management mode is very inefficient.

When we leave, the program is in a state of no use. Then some of the system's background programs, such as disk sorting, anti-virus software, and other programs will be "full speed", resulting in some of our use of the program page has to be squeezed into the hard disk virtual memory. However, when these background programs complete the task, the XP system will not be squeezed into the virtual memory of the page back to memory. So when the computer is used again, the system will be scrambling for temporary deployment, or even hard paging. Causes the program to respond extremely slowly. So it looks like XP has a lot of free memory, and it doesn't really have much effect.

Windows 7 Usage Recommendations

Anyone wants to optimize the means to make their own computer running speed to achieve the most ideal state, and memory is also affecting the speed of the computer is very important factors, we understand the WINDOWS7 memory management mechanism, and then to introduce which methods can accelerate the system.

1. Use Sleep and sleeping more

Since the superfetch to preload after the boot, so we do not recommend the shutdown. Try to use "hibernate" or "sleep" so that superfetch content is preserved. Thus improving speed and efficiency.

2. Use ReadyBoost

A lot of users from XP up because the system memory is not big enough, so can not fully play the function of SuperFetch. We can use the "ReadyBoost" feature to help us solve this problem.

As long as the eligible flash memory can accelerate our system. The ReadyBoost function is to use the capacity of flash memory as the storage space of superfetch pages. But because Microsoft uses the special algorithm, therefore does not affect the flash life. Also, the Flash for ReadyBoost is best 1~2.5 times the physical memory size. If the system physical memory is large enough, there is no need to use ReadyBoost. Right-click on the U disk character selection properties, switch to readyboost a column, speed to achieve the standard U disk can be turned on this function.

Not all USB drives can be used

Through the understanding of SuperFetch, hope more friends into the use of Windows7 team. In fact, the same as windows, different and where to go? Not accustomed to that is temporary. After all, after the ordeal of Vista, Windows7 will also become more mature!

Tips: What is a working set

We can simply think of memory as a combination of "data structure" + "working set", simply put, the working space in memory occupied by the process is called working set during the process of running the application.