Disabling is not a good thing to get out of the misunderstanding of disabling virtual memory.

Recently, we have been talking about the major reduction of DDR memory. ddr266 plunged from the position of more than 400 yuan to around 200 yuan. Many people use MB or even 1 GB of memory, as a result, there is a popular idea among some players, that is, disabling virtual memory, prohibiting file exchanges on Windows pages, and forcing command data to be processed in memory can speed up data read/write efficiency, is that true?

Set according to Application Requirements

The author believes that such a statement should be treated in different situations. It is a good thing to disable it.

First, we need to figure out what is the "Large Memory" configuration. Originally designed windows to use virtual memory itself, because the physical memory is very expensive and generally does not exceed MB, the hard disk space needs to be used as a temporary buffer-that is to say, you should compare the amount of physical memory required for the application with the actual memory you own. If the actual memory you own is less than the application peak, you will be in trouble.

Generally, virtual memory should not be disabled for tasks with a large volume of data, such as a large planar graph or 3D animation rendering. If you need to print documents with a large number of images frequently, disabling virtual memory also causesProgramAn error occurs. A buffer file must be generated before being printed by software such as word and then transmitted to the printer. When the image size is large and the resolution is high, the buffer capacity required is also large, when I used to help the ad artist to design a design drawing, I encountered the situation of printing a graph to generate a temporary file of nearly MB. Because windows and applications also require a certain amount of memory to run, if you disable virtual memory for MB configuration, it is likely that the virtual memory is insufficient in the middle of reporting, forced exit causes waste of printing paper and ink.

Therefore, you must decide whether to disable the virtual memory based on your task application environment. Even if you set the virtual memory size to a fixed value, you must be cautious. Otherwise, the system prompts insufficient virtual memory when running large applications. The entire system will become very slow because of the high CPU usage, now it is not that convenient to change it.

Operating system considerations

In different operating systems, the setting or disabling of virtual memory is also different and cannot be generalized.

Due to architecture problems, Windows 9x/me has inherent limitations on memory larger than MB. If the memory is larger than this quantity, Windows 98 may experience instability and slow startup speed. If you use large memory and disable virtual memory, the unstable factor will be further increased. The memory capacity that Windows 2000/XP can effectively manage is about 1 GB. If the memory size is larger than this quantity, instability may occur, and the motherboard BIOS model and chipset performance may vary.

In addition, Windows is designed to map the memory space allocated to a process to the swap file once a process is found to be inactive, try to empty the physical memory for other active threads, instead of using the physical memory to start using swap files. If you wait until the physical memory is used up and then call it, it will be too late, and data transmission and processing will inevitably stagnate on machines with low configurations. Therefore, disabling virtual memory is, in principle, the most likely cause of Windows exceptions. Even if you do not encounter a failure that cannot be run, the system will frequently prompt you that the virtual memory is insufficient. Please reset the cloud to leave you alone.

How to disable virtual memory

If you really want to disable the virtual memory to speed up the running of your friends who have a lot of memory, you can actually use a compromise to "cheat" windows, it is to draw a part of the physical memory to virtualize it into a physical hard disk:

1. Windows 98

You can add a sentence in config. SYS:
Device = c: \ windows \ ramdrive. sys 23000/E (please set it according to your windows partition)
This statement uses the memory by ramdrive. sys virtualizes a partition, where 23000 is the amount of physical memory you want to use, measured in KB. If you have 1 GB, you can set this number to around 300000 to 500000, that is, 300 ~ 500 mb, and then set the virtual memory to the virtual partition, the program runs completely in the physical memory.

2. Windows 2000/XP

You must rely on third-party tool software to virtualize the physical hard disk, and then put pagefile. set the Sys page file to the virtual disk to achieve the same effect. add a sentence at the bottom of [ENH] in ini, conservativeswapfileusage = 1, so that Windows uses physical memory first, and do not forcibly disable virtual memory swap files.

Conclusion

I believe that the acceleration effect of disabling virtual memory is very limited. In addition, the default settings for windows are generally appropriate, especially for Windows 2000/XP, do not change it at will. Otherwise, it is difficult for you to judge and analyze the problem.

Problem: Memory Fault Analysis

Sometimes, some memory-related fault prompts appear in windows, not necessarily related to memory. Some seemingly memory-independent faults are actually caused by memory and very concealed.

For example, if you change the size of a partition cluster by using tools such as pqpartitioning master, when the cluster is smaller than the default value, Windows 98 may report insufficient memory when running a disk scan, windows 2000 and Windows XP are normal -- that is to say, this has nothing to do with memory.

For another example, when you start Windows, the system will prompt you for a registry error and whether to recover it. If you choose to recover it, restart it again, or the same prompt, but most of them are caused by memory or heat dissipation problems. You need to replace the memory or fan.

Therefore, Windows prompts may mislead users. If the same fault occurs repeatedly, the problem cannot be solved according to the prompts. The possibility of false positives should be considered.