Exchange memory use and the /3GB switch
The /3GB SwitchBy default, Windows can address a total of 4 gigabytes (GB) of virtual address space. By default, 2 GB of this is reserved for the kernel (operating system), and 2 GB is reserved for User mode programs such as Exchange.
When you put a /3GB switch into the Boot.ini file of the operating system, you reallocate the virtual address space distribution to give User mode programs 3 GB of space and limit the kernel to 1 GB. The /3GB switch is only required on computers that contain mailbox stores or public folder stores. This switch is not recommended on computers that do not have mailbox stores or public folder stores.
Important Only use the /3GB switch with the following operating systems:
- Microsoft Windows Server 2003 Datacenter Edition
- Microsoft Windows Server 2003 Enterprise Edition
- Microsoft Windows 2000 Advanced Server
- Microsoft Windows 2000 Datacenter Server
- Microsoft Windows NT 4.0 Enterprise Server
Do not use the /3GB switch with the following operating systems:
- Microsoft Windows 2000 Server
- Microsoft Windows NT 4.0 Server
Exchange on a Windows 2000 Server-Based ComputerThe 2GB virtual memory address limit for User mode programs can contribute to several issues in Exchange when you have more than 1 GB of physical memory installed in your computer.
Exchange calculates the memory that is allocated to database buffers based on the amount of physical memory. Physical memory above 1 GB can cause a disproportionate amount of the 2 GB of virtual memory to be allocated to database buffers. This may cause virtual memory fragmentation problems, performance issues, or "out of memory" issues.
To work around this issue, use one or more of the following methods:
Reduce the Jet DBA SizeYou might be able to reclaim some memory by reducing the JET DBA size. For more information about how to reduce the JET DBA size, click the following article number to view the article in the Microsoft Knowledge Base:
Reduce the Number of maxOpenTables in JETYou might be able to reclaim some memory by reducing the number of maxOpenTables in JET.
Set msExchESEParamMaxOpenTables on each storage group object to a lower value. The default for an 8 proc in Service Pack 2 (SP2) is 85,000. This is reduced to 27,600 in Service Pack 3 (SP3) for 8-procs. The 4-procs number is half of this value.
Note If you continue to experience memory problems, remove some RAM from your server to reduce it to 1GB or less. This helps you to confirm that the situation that is described in this article is causing the issue.
Exchange on a Windows 2000 Advanced Server-Based ComputerWhen a Windows 2000 Advanced Server-based computer has more than 1 GB of physical RAM, use the /3GB switch in the Boot.ini file to give User mode programs such as Exchange to have access to 3 GB of virtual address space. For more information this issue, click the following article number to view the article in the Microsoft Knowledge Base:
Exchange on a Windows 2000 Datacenter Server-Based ComputerUse the /3GB switch with more than 1 GB of physical RAM on a Windows 2000 Datacenter Server-based computer. Exchange requires Service Pack 1 (SP1) to be supported on Windows 2000 Datacenter Server.
The /PAE SwitchPhysical Address Extension (PAE) is a feature of Windows 2000 Datacenter Server and Windows 2000 Advanced Server that makes it possible for programs that were written for this API to use memory above 4 GB. Although there are programs such as Microsoft SQL Server 2000 that were written to take advantage of this API, Exchange 2000 Server is not compatible with it. Because of this, Exchange only addresses 3 GB if you use the /3GB switch.
TroubleshootingProblems that are related to the issues that are described in this article typically become evident as performance problems. To troubleshoot these problems, use the Performance Monitor tool.
You can also use the Virtual Address Dump utility (VADUMP) to troubleshoot problems like this. For more information about the VADUMP tool, click the following article number to view the article in the Microsoft Knowledge Base:
Additional InformationFor more information about the issues that are described in this article, click the following article numbers to view the articles in the Microsoft Knowledge Base:
Article ID: 328882 - Last Review: 12/07/2015 12:34:37 - Revision: 5.4
- kbnosurvey kbarchive kbenv kbinfo KB328882