Severe performance degradation under Windows 2003 due to the Working Set Trimming issue noted in KB956341.
If Microsoft SQL Server in use the following error in SQL Server log:
“A significant part of sql server process memory has been paged out. This may result in a performance degradation.”
Given Microsoft Exchange and other server applications, a sudden drop off in Process Object/Working Set noted via Performance Monitor
Example: Excessive Paging on Exchange 2007
Windows 2003 behavior of paging all process Working Sets to disk in order to satisfy a driver memory request, same requests detailed in KB956341.
This behavior is changed in Windows 2008, please see resolution section below.
Recommended: Migrate to Windows 2008 x64 or 2008 R2 where this issue is sufficiently mitigated by architectural changes in the Windows Memory Manager. On Windows 2008, consider installing the Dynamic Cache Service to moderate Windows Cache usage as a vector for this problem (service not required on 2008R2). Note: Windows 2003 will not be revised with the relevant Windows 2008 and higher changes and the potential root causes under 2003 are varied and hard to detect.
Windows 2003 Known Problem Driver Versions and Configuration Reference:
Contiguous Memory usage by Video Adapters - use /basevideo switch and use Device Manager to change display adapter to “Standard VGA Graphics Adapter”
Note: The above configuration change in the video adapter is particularly important due to other adapters which have boundary restrictions for memory allocations (allocates below 4GB, such as storport.sys). Such restricted drivers may not be changed for older device compatibility reasons. Thus, limiting the usage of contiguous memory <4GB in the video adapter is often the best solution to allow even small allocations (we have seen 8MB) increased chance of success and thus not triggering a Working Set trim. Also, we recommend removing any extraneous Network Adapter or Storage Adapter instances. Extra adapters of this type will each consume a share of memory in this address range, increasing probability to encounter this problem under Windows 2003.
Upgrade from Windows 2003 SP1 Msgina.dll (fixed in Windows 2003 SP2)