Article ID: 197379
Article Last Modified on 7/23/2007
APPLIES TO
- Microsoft Windows Server 2003, Standard Edition (32-bit x86)
- Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
- Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
- Microsoft Windows 2000 Server
- Microsoft Windows 2000 Advanced Server
- Microsoft Windows 2000 Professional Edition
- Microsoft Windows 2000 Datacenter Server
- Microsoft Windows NT Workstation 4.0 Developer Edition
- Microsoft Windows NT Server 4.0 Standard Edition
- Microsoft Windows NT Server 4.0 Enterprise Edition
- Microsoft Windows NT Server 4.0, Terminal Server Edition
- Microsoft Windows NT Workstation 3.51
- Microsoft Windows NT Server 3.51
This article was previously published under Q197379
For a Microsoft Windows XP version of this article, see 314482.
SUMMARY
By default, Windows Puts the paging file on the boot partition where the operating system is installed and creates a default size of the paging file that is 1.5 times the physical RAM, up to a maximum of 4095 MB. However, placing the paging filefile on the boot partition does not optimize performance because Windows has to perform disk I/O on both the system directory and the paging file. Therefore, it is recommended that you place the paging file on a different partition and different physical hard disk drive so that Windows can handle multiple I/O requests more quickly.
However, completely removing the paging file from the boot partition does not allow Windows to create a crash dump file (Memory.dmp) should a kernel mode STOP error occur. Not having this crash dump file could lead to extended server downtime should the STOP require a debug to be performed.
The optimal solution, other than the solution of adding more physical memory, is to do the following:
- Create one paging file on the boot partition by using the default settings.
- Create another paging file on a less frequently used partition on a separate physical disk or RAID volume.
You can create additional paging files for each separate physical disk or RAID volume.
Windows will use the paging file on the less frequently used partition over the paging file on the heavily used boot partition. Windows uses an internal algorithm to determine which page file to use for virtual memory management. In the above scenario, the following goals of the page file would be served:
- The system will be properly configured to capture a Memory.dmp file should the computer experience a kernel mode STOP error.
- The page file on the less frequently used partition will be used the majority of the time because it is not on a busy partition.
MORE INFORMATION
Another advantage of using a paging file on its own partition is that the paging file will not become fragmented. If the paging file is on a partition with other data, the paging file might experience fragmentation as it expands to satisfy the extra virtual memory required. A defragmented paging file leads to faster virtual memory access and improves the chances of capturing a dump file without significant errors.
Additional query words: page file multiple pagefile dump
Keywords: kbinfo KB197379
