Generation, impact, processing, and others of fragments

Author: Steven Source: MS Community

I. Under what circumstances are fragments of paging files generated?

Generally, whether it is based on the system's default "windows Management paging file size" or "Custom", the paging file has an initial value and a maximum value. By default, the initial value is 1.5 times the physical memory of the system. For example, if you have 196 MB of physical memory, the initial value of the paging file is MB. This is generally the size of the space occupied by paging files on the hard disk. When the system requires a larger virtual memory, it increases the size of the paging file by itself to make it larger than 196M to meet the needs. In this case, the paging file fragments may be generated. In turn, if you set the initial value of the paging file to a greater value based on your actual needs, so that the system does not need to increase the size of the paging file on its own, no fragments will be generated. This is why setting the size of the paging file to a fixed value does not cause fragmentation.

2. Will fragments still be generated after the size of the paging file is fixed? What are the potential problems with this setup?

To fix the size of a paging file, set the initial value and maximum value of the paging file to the same. As discussed above, no file fragments will be generated. Because the system no longer adjusts its size. This leads to a problem. You need to set this fixed value to a greater value than you actually need. Otherwise, the out
Memory error; because it is fixed, the system cannot adjust its size. This problem is often exposed when you need to change your actual needs, such as using the system to run programs that consume a large amount of memory, such as audio and video editing and graphic design. Therefore, if you want to set it like this, you need to have a number in mind.

3. Is there a way to avoid fragmentation of paging files as much as possible?

Two aspects: increase the physical memory, and set a reasonable Initial Value for paging files.

First of all, windows programs always take advantage of the physical memory at runtime. Even if the physical memory is exhausted, when a new program runs, it also schedules the physical memory as much as possible. If the physical memory is not enough, the paging file is scheduled, and the virtual memory is used by the hard disk space, you will feel that the system is running at a lower speed. Therefore, increasing the physical memory is beneficial both in improving performance and in terms of file fragmentation. Generally, increasing the physical memory improves the performance much more than upgrading the CPU. Of course, this requires silver.

Second, the initial values of paging files. As mentioned above, fragments are easily generated if the initial value is small. Because the system will adjust the size of the paging file as needed. Therefore, from the perspective of file fragmentation, you should set an appropriate initial value as needed. However, it may also occupy more hard disk space.

4. Does the fragmentation of paging files significantly affect system performance?

In general, paging files may produce some file fragments, but they generally do not have a "sensory" impact on system performance, or they have little impact and do not need to be processed. Besides, as mentioned in Inside Out,

In practice, the design of the page file
Is such that it tends to use large blocks of disk space, and as a result
Impact of fragmentation on the page file is minimal. You might notice a very
Small performance hit when Windows increases the size of the page file,
Thats a one-time operation and wont affect everyday performance.

5. What should I do if there are a large number of fragments in the paging file?

In rare cases, if the paging file actually generates a large number of fragments, this will affect the performance and need to be processed.

We know that the system's built-in disk sorting program cannot process the fragments of paging files. Here is a work und:

First, follow the http://support.microsoft.com /? Id = 307886, move the paging file from the startup partition to another partition, and set "No paging file" in the startup partition ". After the restart, check whether there are paging files in the boot partition. If yes, delete the files, run the disk sorting program, and sort the fragments in the boot partition. After that, move it back to KB307886. This method can also meet the user psychology of "striving for perfection" to a great extent.

5. Why does Microsoft recommend that the initial values of paging files be at least 1.5 times that of physical memory? Can I set it to a smaller value?

I think this is 1.5 times: in the default settings of Windows XP, if the system fails or fails, the system is completely converted to the storage file. If you want to write a fully-converted storage file, you need to start the partition's paging file size at least equal to the physical memory size, otherwise it will not work. Microsoft recommends that the initial size of the paging file be 1.5 times that of the physical memory, probably because of this. After understanding this, you will also know that you can set a smaller value, but you must change the system's write-to-storage file settings before setting. It should be noted that the initial value setting is small, and fragments may be generated more easily.

This issue does have some controversy. For example, someone suggested that the initial values of paging files should not be set based on the physical memory size, but should be set based on the actual situation or actual needs. This statement is not a big problem. However, Microsoft may consider it. The company always provides users with the most secure suggestions for using their products.

6. Do household users need to intervene in paging file settings?

Remember this sentence first: as a common user, you do not have to pay too much attention to the system's paging file, it also does not require painstaking research on how to set it, and worry too much about its fragmentation issues. You should not try to use it to significantly improve system performance. It does not exist.

One exception is that the partition space is tight and you can move it to another partition. From the perspective of optimization, the updated 314482 KB (2.0) method has a precondition: when the computer has two or more hard disks, you have the opportunity to use this method. Of course, if you have the opportunity or the conditions, you can set the paging file using the method in it.

If you find that the system runs slowly due to the virtual memory, no matter how you set this paging file or "process" its fragments, you will not get satisfactory results. In this case, we recommend that you increase the physical memory to meet your actual needs.