Microsoft Windows Server operating systems that support hot-add memory can unintentionally deplete Exchange Server 2003's kernel-paged pool memory and cause serious performance problems. Prevent and resolve hot-add memory issues on Exchange Server with these performance troubleshooting options.
Windows Server 2003 Datacenter and Enterprise Editions support hot-add memory, a hardware-level feature that lets an administrator add memory to an operating system without having to shut it down or take it offline.
Hot-add memory is useful, but it can cause quirky Exchange Server 2003 behavior. Problems actually arise from the way Windows Server 2003 manages the hot-add memory feature, but they most often manifest through Exchange Server. Exchange inexplicably fails to start or crashes for no apparent reason on Windows Server operating systems that have hot-add memory functionality.
Hot-add memory support, enabled by default, sets aside a certain amount of kernel-level memory for future memory allocation. Consequently, kernel memory may be set aside and never used, and the kernel-paged pool memory may be depleted faster than the operating system anticipates.
Microsoft Exchange and SQL Server administrators have to wrestle with this issue, since both Exchange Server and SQL Server aggressively use kernel-paged pool memory.
Windows 32-bit systems with 3 GB or more RAM installed experience a similar performance problem. On 32-bit systems with more than 3 GB RAM, the kernel
To continue reading for free, register below or login
To read more you must become a member of SearchExchange.com
-paged pool also get used up fairly quickly. The solution is to modify the size of the paged pool and a number of other kernel-level functions by using the /3GB and /USERVA boot switches.
Unfortunately, this solution doesn't work for Windows systems with hot-add memory support enabled. The paged-pool depletion problem gets magnified instead.
As discussed in the Microsoft Exchange Team blog post about Windows 2003 kernel memory issues and Exchange 2003, Windows attempts to reserve kernel space for the maximum amount of physical memory that can be added to the machine.
For example, if you have a Windows server that can support up to 64 GB of hot-add memory, but only 4 GB is actually installed, the operating system will set aside enough kernel-paged pool memory to support all 64 GB anyway! This means that a 64 GB allocation can use up as much as 30% of your kernel's paged pool.
Microsoft offers several possible solutions to performance problems caused by hot-add memory enabled systems:
About the author: Serdar Yegulalp is editor of Windows Insight, a newsletter devoted to hints, tips, tricks, news and goodies for all flavors of Windows users.
Do you have comments on this tip? Let us know.
Please let others know how useful this tip was via the rating scale below. Do you know a helpful Exchange Server, Microsoft Outlook or SharePoint tip, timesaver or workaround? Email the editors to talk about writing for SearchExchange.com.
