Recently, the topic that everyone often talks about is the large price reduction of DDR memory. DDR266 has plummeted from 400 yuan to 200 yuan. Many people use 512MB or even 1GB of memory. Therefore, there is a view that is popular among some players. It is said that disabling virtual memory, prohibiting Windows page file exchange, and forcing command data to be processed in memory can speed up data reading and writing efficiency. Is this true? According to the application needs to set up the author believes that this statement should be treated separately, can not just say that disabling is a good thing. First, figuring out what a "big memory" configuration is. The original design of Windows uses virtual memory itself because physical memory is very expensive, generally does not exceed 128MB capacity, and requires hard disk space for temporary buffering - that is, you should use how much physical memory the application needs and the memory it actually owns. A comparison, if the actual memory is less than the application peak, you will run into trouble. In general, virtual memory should not be disabled if you want to perform large-format tasks such as large-format graphics and 3D animation rendering. If you often want to print a document with a large number of images, disabling virtual memory will also cause errors in the program. Because the software like Word is to generate a buffer file before printing, and then transfer it to the printer. When the image size is larger and the resolution is higher, the buffer capacity required is also large. When I used to help the advertising artist to design the drawing, I encountered a situation in which a picture was printed to generate nearly 300MB of temporary files. Because Windows and the application itself also need a certain amount of memory to run, if you are 512MB configuration, disable virtual memory, it is very likely that the virtual memory is insufficiently reported midway, forcibly exiting, causing waste of printing paper and ink. Therefore, you must decide whether to disable virtual memory based on your task application environment. Even if you set the virtual memory size fixedly, you must be cautious. Otherwise, the virtual memory will be insufficient when running large application software. The whole system will become very slow due to the high CPU usage. Not so convenient. Considering the factors of the operating system Under different operating systems, the setting or disabling of virtual memory is different and cannot be generalized. Because of the architecture problem, Windows 9x/Me has inherent defects in memory larger than 256MB. More than this amount of memory, Windows 98 will be unstable and slow to start. If you use large memory plus disable virtual memory, the instability factor will increase further. Windows 2000/XP can effectively manage a memory capacity of about 1 GB. If this number is greater than this number, it will be unstable, and it will vary depending on the motherboard BiOS model and chipset performance. In addition, the design of Windows itself is that once a process is found to be inactive, it will map the memory space allocated to it to the swap file, freeing physical memory to other active threads as much as possible, not using physics. The memory starts to use the swap file. Because it is too late to wait until the physical memory is used up, it will inevitably cause data transmission and processing stagnation on the lower configuration machine. Therefore, in principle, virtual memory is forbidden to cause Windows abnormality. Even if there is no fault that cannot be run, the virtual memory will be frequently prompted. Please reset the cloud to make you feel overwhelmed. How to disable virtual memory For friends who have a large amount of memory, if you really want to disable virtual memory to speed up the operation, you can actually "spoof" Windows by compromise, that is, divide the physical memory into a virtual 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 own Windows partition) This sentence is to use the memory by Ramdrive.sys virtual Out of a partition, where 23000 is how much physical memory you want to use, the unit is KB, if you have 1GB, you can set this number to 300,000 to 500,000, that is, 300 to 500MB, and then set the virtual memory to the virtual partition. Onwards, the program runs entirely in physical memory. 2. Windows 2000/XP must rely on third-party tool software to virtualize the physical hard disk, and then set the Pagefile.sys page file to the virtual disk to achieve the same effect; or "[386enh]" in System.ini Add a sentence at the bottom, ConservativeSwapfileUsage=1, let Windows use physical memory first, try not to force the virtual memory swap file directly. Conclusion I believe that the acceleration effect of disabling virtual memory is very limited, and the default setting of Windows is more appropriate, especially the default setting of Windows 2000/XP is very good for virtual memory management. Try not to change it at will, otherwise there will be problems. It is difficult to judge and analyze. Some fault analysis about memory Sometimes, Windows has some memory-related fault prompts, not necessarily related to memory; and some seemingly memory-independent faults are really memory-induced and very concealed. For example: you use the PQ partition master and other tools to change the size of the partition cluster. When the cluster is smaller than the default value, Windows 98 running disk scan may report insufficient memory, but under Windows 2000 and Windows XP it is normal - that is Said, this has nothing to do with memory. For example: sometimes when booting into Windows, the system will prompt you for a registry error, whether to restore, when you choose to restore, restart again, or the same prompt, but this fault is mostly caused by memory or heat dissipation. You need to replace the memory or the fan. Therefore, Windows prompts sometimes mislead users. If the same type of fault occurs repeatedly, follow the prompts, you should not consider the possibility of Windows false positives.