Detailed explanation of Vista/Win7 memory management

Detailed explanation of Vista/Win7 memory management, for Windows Vista, Windows7 memory usage, most of the users upgrading from XP think: the free memory should be as much as possible when the system is idle. In the era of 7 (more precisely, after Vista), this concept of change should be left in everyone's memory. So here is the Windows7 new memory management mechanism "Superfetch" introduced to everyone, let everyone understand the reason why Windows7 memory is large.

What is the difference between Windows 7 memory management

"Superfetch" is not a new technology, it has been adopted in the era of Vista, but the number of people who have used Vista is relatively small, and the XP era The various computer skills are still deeply rooted in the hearts of the people, so many people are wondering why Windows 7 memory is so large.

Superfetch memory management mechanism will pre-load the application page that the user may use with memory free space; avoid the system from calling the page of the hard disk as much as possible; let the application open at the fastest speed; The computer is idle for a long time and the sudden use becomes responsive; after exiting the large application, the page that was previously forced to transfer to the virtual memory is actively reloaded into the memory. This seems to be a bit more professional, so looking down, it will be a good understanding of these features.

Why does it feel slow to start the program for the first time?

I believe everyone has had a similar experience. When I boot up, the first time I run a program, for example, it is word, it may take 5 seconds to start. When I turn it off and then turn it on, it may take only 2 seconds. If I don't close it, just open another Word file, it's faster.

What is the reason for this?

When we booted up, there was no Word employee (page) in the working set, and he was still at home (hard disk). So when I summoned him, it went from home to the office (working set). This process is called hard paging, and of course it takes a long time. 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, so he does not have to come from home. It is straightforward to introduce directly from the data structure. When you don't close the program Word, he doesn't have to make way for other programs. It still exists in the office (working set), and it will be faster when he summons him. Such a process of "re-recalling data from the hard disk, but re-attaching pages in the data structure to the working set" is called soft paging. Everyone knows that the memory speed is much faster than the hard disk, so the use of "soft paging" is the reason why the second time the program is running very fast.

Windows 7 memory is a big reason

Now we know that when there is a program page in memory, the program will start faster. And "Superfetch" in Windows7 already has the learning function. Since the first time I used Windows 7, Superfetch began to record our usage habits, and the pages of the programs we use often are loaded in advance after booting, then when we first When you open the program once, you get the same speed as the second one. So these preloaded pages will make our memory footprint more. Simply put, let all the program operations in memory, avoid using hard disk hard paging space, which is why Windows 7 takes up a lot of memory.

View preloaded memory

In the XP era, maybe you have had a similar experience: when you start using some programs, you leave because of something. When I came back, I found that the system responded very slowly, especially bad. This is due to the very inefficient memory management mode of XP.

When we left, the program was not in use. At this time, some background programs of the system, such as defragmentation and anti-virus software, will run at full speed, causing some of the program pages we use to be squeezed into the virtual memory of the hard disk. However, when these daemons complete the task, the XP system does not import the pages that were previously pushed into virtual memory back into memory. So when you use the computer again, the system will be busy with the temporary deployment, or even hard page. The program response is extremely slow. So it seems that XP has a lot of free memory, and in fact it doesn't make much difference.

Windows 7 Usage Suggestions

Everyone wants to optimize their computer to run at the optimal speed, and memory is a very important factor affecting the speed of the computer. Understand the memory management mechanism of Windows 7, and then introduce which methods can accelerate the system.

1, use more sleep and sleep

Because SuperFetch is preloaded after booting, it is recommended that you do not shut down. Try to use "hibernate" or "sleep" so that SuperFetch's preloaded content is preserved. Thereby increasing speed and efficiency.

2. Using ReadyBoost

A lot of users who have been upgraded from XP cannot fully play SuperFetch because the system's memory is not big enough. We can use the "ReadyBoost" feature to help us solve this problem.

As long as the qualifying flash memory can accelerate our system. The ReadyBoost feature uses the capacity of the flash memory as the storage space for SuperFetch preloaded pages. However, since the soft algorithm uses a special algorithm, it does not affect the life of the flash memory. Also, the flash memory for ReadyBoost is preferably 1 to 2.5 times the physical memory size. If the system's physical memory is large enough, there is no need to use ReadyBoost. Right click on the U disk drive to select the attribute and switch to the readyboost column. This function can be enabled for the U disk with the standard speed.

Not all U-disks can be used

After learning about SuperFetch, I hope more friends will enter the team using Windows7. In fact, the same as Windows, where can you go? Not accustomed to is a temporary one. After all, after Vista's tempering, Windows 7 will become more mature!

Tips: What is a working set

We can simply understand memory as a combination of "data structure" + "working set", in simple terms, the process of the application is running The workspace in the occupied memory is called the working set.