2003最大内存支持

2003最大内存支持 How much memory is supported by Win2003 server Source: author: Internet anonymous time: 12-31 22:35:37 review: big in small 】 【 recently proposed to buy the server, the server performance because of the increase of traffic need to be considered two of the four core CPU, memory, we are going to use about 16 gb of memory, be afraid does not support so implementation according to our experience, under the query win2003 enterprise edition is a 32-bit can support to 32 gb of memory, a 64 - bit system can support 64 g, but 64 - bit operating system, many software do not support, so we suggest use win2003 32-bit system, the highest supported 32 gb of memory, in general, will be enough, if the installation does not support, installation to upgrade to the sp2 was no problem in general Why does Windows 2003 Server support more than four gigabytes of memory? It is true that 32bit versions can support 32gb of memory. This is because MS PAE function for Server system development, namely the physical address extension, physical address extension, this function can be expanded to about 32 bit memory addressing space 48 bit or 64 bit, maximum support this theory of memory to 16 * 1024 * 1024 * 1024 g = such a large space, and Microsoft will deliberately its limit to 32 gb, 64 - bit systems is limited to 64 gb. Limiting conditions inconsistent version is produced to distinguish different feeling, otherwise no one will choose the 64 - bit server system (now also few enterprises choose 64 - bit, 32 bit will be enough, ^_^). Why is it limited? No motherboard can support so much memory right now No application requires such a large amount of memory, and servers that require large memory are generally used by the state, and their servers do not use Windows No test environment Microsoft can't verify that the system is stable after more than 64G of memory Windows Server 2003 Enterprise Edition: * supports 8 node clusters, NUMA; Support 8-way SMP * memory support: (i386) 32-bit support for 32GB memory (X64) 64-bit support for 64GB memory Windows 2003 support only small memory by default mode (3 g) is greater than 3 g need to edit the Boot. Ini add/pae parameter open the large memory model to support more than 3 g memory, according to the above operation edit Boot. Ini restart there is still a problem is compatible with your memory. Here is a 2003 Boot. Ini example: [the boot loader] Timeout = 0 Default = multi (0) disk (0) rdisk (0) partition (1) \ WINDOWS [operating systems] Multi (0) disk (0) rdisk (0), partition (1) \ WINDOWS = "WINDOWS Server 2003, Enterprise"/fastdetect/usepmtimer/NoExecute = OptIn/PAE Windows Server 2003 Web page: provides Web hosting and service platforms for rapid development, deployment of Web services and applications. Supports 2 SMP (symmetric multiprocessing) system and 2GB of memory. Windows Server 2003 standard edition: for small and medium enterprises and departmental applications. Supports 4-way SMP and 4GB memory. Windows Server 2003 enterprise edition: for the center and large organization, there are 32-bit and 64-bit versions. Supports 8 node clusters, NUMA; Support for 8-way SMP, 32 of which support 32GB of memory, 64 bit support for 64GB memory. Windows Server 2003 data center version: for enterprises that require strong scalability and high availability, there are 32-bit and 64-bit versions. 32-bit support for 32-path SMP and 64GB memory; 64-bit support for 64 SMP and 512GB memory; Both versions support the 8 node cluster, NUMA To enable Windows 2003 support for more than 4GB of physical memory, the parameter/pae must be added to the boot.ini file. Server has just come to buy just found this problem, why only 4 gb of memory motherboard play good recognition into 3 G, three back four times change BIOS can only let the mainboard as 3.3 G and 3.5 G or so, it's very annoying. .. Turned out to be some servers have memory empty, so 3.3 G - 3.8 G is normal, this part of the empty memory as the hardware consumption, too much bad will upgrade motherboard BIOS and firmware of the array card is ok. If it is an XP or 2003 series, you will have to add/PAE parameters to the BOOS. INI to access the extended memory properly. More than 1G will be added/USERVA = 3030 to optimize the configuration of virtual memory. An important security feature in win2003 SP1 - "data execution protection capability (" : DEP)". You can find it in "control panel, system, advanced, Settings, data enforcement protection". When you switch between these two items, "/ NoExecute = OptIn" will also become "/ NoExecute = Optout". Note: this function need hardware support: including AMD Athlon 64, AMD Opteron, Intel itanium and itanium 2, it is said that nVIDIA, VIA, the company also plans to join the technology in its chips. It is recommended that ordinary users not modify it or cause the system to run unstable. / NoExecute = alwaysoff is to close the data to perform protection / NoExecute = OptIn says the first item is "just for..." The item / NoExecute = Optout is the second option / noexecute = AlwaysOff, which is the equivalent of shutting down the DEP and EVP functions, and the programs that are blocked by them are running normally / NoExecute = OptOut -- DEP is opened, and all services use DEP V if you have more than 3G server memory, the system is Win2003 if you don't support 3G The profile This article introduces the physical address extension (PAE) and the address window extension (AWE) and explains how they work together. This article also discusses the limitations of memory usage inherent in the 4 GB range inherent in the 32-bit operating system. For more information PAE improves the ability of the IA32 processor to handle physical memory greater than 4 GB. Microsoft Windows 2000 Advanced Server, Microsoft Windows 2000 Datacenter Server, Microsoft Windows Server 2003 Enterprise Edition and Microsoft Windows Server 2003 Datacenter Edition can use PAE to leverage more than 4GB of physical memory. To enable the PAE, you need to use the/PAE parameter in the boot.ini file. Note: the Windows Server 2003 Enterprise Edition and Windows Server 2003 Datacenter Edition automatically enable PAE only when the Server USES the hot added memory device. In this case, you do not need to use the/PAE switch on the system configured to use the hot added memory device. In other cases, you must use the/PAE switch in the boot.ini file to use more than 4GB of memory. Typical case is that, in the process of running under Windows 2000 or Windows Server 2003 can be accessed at most 2 GB of memory address space (if not use the / 3 GB parameters), some of which is memory physical memory, the other is virtual memory. The more programs run (and therefore the more processes), the more the memory address space is closer to 2 GB. When this happens, the paging process increases significantly and negatively impacts performance. The Windows 2000 and Windows Server 2003 memory manager provide more physical memory to the program using the PAE. This reduces the need to exchange page file memory, thereby improving performance. The program itself does not know the actual memory size. All memory management and PAE memory allocations are handled by the memory manager, regardless of the running program. When using / 3GB parameters, this information is valid for the running program. A program that requires 3 GB of memory is more likely to have more memory in physical memory, Not in the virtual memory of paging. This will enhance the performance of programs that can use / 3GB parameters. The exception is when the / 3GB parameter is used with the/PAE parameter. In this case, the operating system will not use any more than 16 GB of memory. This behavior is caused by the kernel virtual memory space. Therefore, if the system USES the Boot. Ini files in the / 3 GB restart, and the system more than 16 GB of physical memory, the operating system does not use additional physical random access memory (RAM). If you don't use the / 3GB switch when you restart the computer, you will be able to use all the physical memory. AWE is the memory manager function of a set of application programming interface (API), it can make the program more memory addressing - more than standard 32-bit addressing the 4 GB of memory space. AWE enables the program to keep physical memory in non-paging memory, and then dynamically map non-page memory parts to the program's memory work set. This process enables memory-intensive programs, such as large database systems, to retain a large amount of physical memory for the data without having to exchange paging files for use. Instead, the data is exchanged at work, and the memory is more than 4 GB. In addition, the memory range over 4 GB is open to the memory manager, and AWE works through the PAE. Without PAE, AWE cannot hold more than 4 GB of memory. Here is an example of a boot.ini file, with the PAE switch added: [the boot loader] Timeout = 30 Default = multi (0) disk (0) rdisk (0) partition (2) \ WINDOWS [operating systems] Multi (0) disk (0) rdisk (0) partition (2) \ WINDOWS = "WINDOWS Server 2003, Enterprise"/fastdetect/PAE Warning: the contents of the boot.ini file vary depending on your configuration. For more information, click the article number below to see the corresponding article in the Microsoft knowledge base: How to edit the boot.ini file in Windows Server 2003 () In short, the PAE is a function of Windows 2000 and Windows Server 2003 memory manager, which provides more physical memory for programs requesting memory. Program does not know what it is to use some within the scope of the greater than 4 GB of memory, as the program does not know it request of memory is actually in the page file. AWE is an API set that enables programs to retain large memory blocks. The reserved memory is non-paginated and can only be used by the program. For more information about AWE and PAE, click the article number below to see the corresponding article in the Microsoft knowledge base: 268363 () the Intel physical address extension (PAE) in Windows 2000 If you add more memory to the system, the BIOS may recognize all physical RAM installed on the server, and Windows will only recognize some of the RAM. If the server has a redundant memory function or memory image enabled, all of the remaining memory may not be visible to Windows. A memory block that provides a failover for the system when a memory block fails. The memory image breaks the memory block into a mirrored set. Both functions are enabled or disabled in the BIOS and cannot be accessed through Windows. To modify the Settings of these functions, you may have to refer to the system user manual or OEM website. In addition, you may have to contact the hardware vendor. For example, if a running system installed 4 gb of RAM, then add another 4 gb of RAM, Windows may only identify the 4 gb or 6 gb of physical memory, but not all of the 8 gb. Redundant memory functions or memory mirroring functions may be enabled on new memory blocks when you are unknown. These symptoms are similar to the symptoms of not adding/PAE switches to the boot.ini file