Memory Limits for Windows and Windows Server Releases

This topic describes the memory limits for supported Windows and Windows Server releases.

Limits on memory and address space vary by platform, operating system, and by whether the IMAGE_FILE_LARGE_ADDRESS_AWARE value of the LOADED_IMAGE structure and 4-gigabyte tuning (4GT) are in use. IMAGE_FILE_LARGE_ADDRESS_AWARE is set or cleared by using the /LARGEADDRESSAWARE linker option.

4-gigabyte tuning (4GT), also known as application memory tuning, or the /3GB switch, is a technology (only applicable to 32 bit systems) that alters the amount of virtual address space available to user mode applications. Enabling this technology reduces the overall size of the system virtual address space and therefore system resource maximums. For more information, see What is 4GT.

Limits on physical memory for 32-bit platforms also depend on the Physical Address Extension (PAE), which allows 32-bit Windows systems to use more than 4 GB of physical memory.

Memory and Address Space Limits

The following table specifies the limits on memory and address space for supported releases of Windows. Unless otherwise noted, the limits in this table apply to all supported releases.

Memory typeLimit on X86Limit in 64-bit Windows
User-mode virtual address space for each 32-bit process2 GB
Up to 3 GB with IMAGE_FILE_LARGE_ADDRESS_AWARE and 4GT
2 GB with IMAGE_FILE_LARGE_ADDRESS_AWARE cleared (default)
4 GB with IMAGE_FILE_LARGE_ADDRESS_AWARE set
User-mode virtual address space for each 64-bit processNot applicableWith IMAGE_FILE_LARGE_ADDRESS_AWARE set (default):
x64: 8 TB
Intel Itanium-based systems: 7 TB
Windows 8.1 and Windows Server 2012 R2: 128 TB

2 GB with IMAGE_FILE_LARGE_ADDRESS_AWARE cleared
Kernel-mode virtual address space2 GB
From 1 GB to a maximum of 2 GB with 4GT
8 TBWindows 8.1 and Windows Server 2012 R2: 128 TB
 
Paged pool384 GB or system commit limit, whichever is smaller. Windows 8.1 and Windows Server 2012 R2: 15.5 TB or system commit limit, whichever is smaller.
Windows Server 2008 R2, Windows 7, Windows Server 2008 and Windows Vista: Limited by available kernel-mode virtual address space. Starting with Windows Vista with Service Pack 1 (SP1), the paged pool can also be limited by the PagedPoolLimit registry key value.
Windows Home Server and Windows Server 2003: 530 MB
Windows XP: 490 MB
 
384 GB or system commit limit, whichever is smaller Windows 8.1 and Windows Server 2012 R2: 15.5 TB or system commit limit, whichever is smaller.
Windows Server 2008 R2, Windows 7, Windows Server 2008 and Windows Vista: 128 GB or system commit limit, whichever is smaller
Windows Server 2003 and Windows XP: Up to 128 GB depending on configuration and RAM.
 
Nonpaged pool75% of RAM or 2 GB, whichever is smaller. Windows 8.1 and Windows Server 2012 R2: RAM or 16 TB, whichever is smaller (address space is limited to 2 x RAM).
Windows Vista: Limited only by kernel mode virtual address space and physical memory. Starting with Windows Vista with SP1, the nonpaged pool can also be limited by the NonPagedPoolLimit registry key value.
Windows Home Server, Windows Server 2003 and Windows XP: 256 MB, or 128 MB with 4GT.
 
RAM or 128 GB, whichever is smaller (address space is limited to 2 x RAM) Windows 8.1 and Windows Server 2012 R2: RAM or 16 TB, whichever is smaller (address space is limited to 2 x RAM).
Windows Server 2008 R2, Windows 7 and Windows Server 2008: 75% of RAM up to a maximum of 128 GB
Windows Vista: 40% of RAM up to a maximum of 128 GB.
Windows Server 2003 and Windows XP: Up to 128 GB depending on configuration and RAM.
 
System cache virtual address space (physical size limited only by physical memory)Limited by available kernel-mode virtual address space or the SystemCacheLimit registry key value.
Windows 8.1 and Windows Server 2012 R2: 16 TB.
Windows Vista: Limited only by kernel mode virtual address space. Starting with Windows Vista with SP1, system cache virtual address space can also be limited by the SystemCacheLimit registry key value.
Windows Home Server, Windows Server 2003 and Windows XP: 860 MB with LargeSystemCache registry key set and without 4GT; up to 448 MB with 4GT.
 
Always 1 TB regardless of physical RAM Windows 8.1 and Windows Server 2012 R2: 16 TB.
Windows Server 2003 and Windows XP: Up to 1 TB depending on configuration and RAM.
 

 

Physical Memory Limits: Windows 10

The following table specifies the limits on physical memory for Windows 10.

VersionLimit on X86Limit on X64
Windows 10 Enterprise4 GB6 TB
Windows 10 Education4 GB2 TB
Windows 10 Pro for Workstations4 GB6 TB
Windows 10 Pro4 GB2 TB
Windows 10 Home4 GB128 GB

 

Physical Memory Limits: Windows Server 2016

The following table specifies the limits on physical memory for Windows Server 2016.

VersionLimit on X64
Windows Server 2016 Datacenter24 TB
Windows Server 2016 Standard24 TB

 

Physical Memory Limits: Windows 8

The following table specifies the limits on physical memory for Windows 8.

VersionLimit on X86Limit on X64
Windows 8 Enterprise4 GB512 GB
Windows 8 Professional4 GB512 GB
Windows 84 GB128 GB

 

Physical Memory Limits: Windows Server 2012

The following table specifies the limits on physical memory for Windows Server 2012. Windows Server 2012 is available only in X64 editions.

VersionLimit on X64
Windows Server 2012 Datacenter4 TB
Windows Server 2012 Standard4 TB
Windows Server 2012 Essentials64 GB
Windows Server 2012 Foundation32 GB
Windows Storage Server 2012 Workgroup32 GB
Windows Storage Server 2012 Standard4 TB
Hyper-V Server 20124 TB

 

Physical Memory Limits: Windows 7

The following table specifies the limits on physical memory for Windows 7.

VersionLimit on X86Limit on X64
Windows 7 Ultimate4 GB192 GB
Windows 7 Enterprise4 GB192 GB
Windows 7 Professional4 GB192 GB
Windows 7 Home Premium4 GB16 GB
Windows 7 Home Basic4 GB8 GB
Windows 7 Starter2 GBN/A

 

Physical Memory Limits: Windows Server 2008 R2

The following table specifies the limits on physical memory for Windows Server 2008 R2. Windows Server 2008 R2 is available only in 64-bit editions.

VersionLimit on X64Limit on IA64
Windows Server 2008 R2 Datacenter2 TB 
Windows Server 2008 R2 Enterprise2 TB 
Windows Server 2008 R2 for Itanium-Based Systems 2 TB
Windows Server 2008 R2 Foundation8 GB 
Windows Server 2008 R2 Standard32 GB 
Windows HPC Server 2008 R2128 GB 
Windows Web Server 2008 R232 GB 

 

Physical Memory Limits: Windows Server 2008

The following table specifies the limits on physical memory for Windows Server 2008. Limits greater than 4 GB for 32-bit Windows assume that PAE is enabled.

VersionLimit on X86Limit on X64Limit on IA64
Windows Server 2008 Datacenter64 GB1 TB 
Windows Server 2008 Enterprise64 GB1 TB 
Windows Server 2008 HPC Edition 128 GB 
Windows Server 2008 Standard4 GB32 GB 
Windows Server 2008 for Itanium-Based Systems  2 TB
Windows Small Business Server 20084 GB32 GB 
Windows Web Server 20084 GB32 GB 

 

Physical Memory Limits: Windows Vista

The following table specifies the limits on physical memory for Windows Vista.

VersionLimit on X86Limit on X64
Windows Vista Ultimate4 GB128 GB
Windows Vista Enterprise4 GB128 GB
Windows Vista Business4 GB128 GB
Windows Vista Home Premium4 GB16 GB
Windows Vista Home Basic4 GB8 GB
Windows Vista Starter1 GB 

 

Physical Memory Limits: Windows Home Server

Windows Home Server is available only in a 32-bit edition. The physical memory limit is 4 GB.

Physical Memory Limits: Windows Server 2003 R2

The following table specifies the limits on physical memory for Windows Server 2003 R2. Limits over 4 GB for 32-bit Windows assume that PAE is enabled.

VersionLimit on X86Limit on X64
Windows Server 2003 R2 Datacenter Edition64 GB
(16 GB with 4GT)
1 TB
Windows Server 2003 R2 Enterprise Edition64 GB
(16 GB with 4GT)
1 TB
Windows Server 2003 R2 Standard Edition4 GB32 GB

 

Physical Memory Limits: Windows Server 2003 with Service Pack 2 (SP2)

The following table specifies the limits on physical memory for Windows Server 2003 with Service Pack 2 (SP2). Limits over 4 GB for 32-bit Windows assume that PAE is enabled.

VersionLimit on X86Limit on X64Limit on IA64
Windows Server 2003 with Service Pack 2 (SP2), Datacenter Edition64 GB
(16 GB with 4GT)
1 TB2 TB
Windows Server 2003 with Service Pack 2 (SP2), Enterprise Edition64 GB
(16 GB with 4GT)
1 TB2 TB
Windows Server 2003 with Service Pack 2 (SP2), Standard Edition4 GB32 GB 

 

Physical Memory Limits: Windows Server 2003 with Service Pack 1 (SP1)

The following table specifies the limits on physical memory for Windows Server 2003 with Service Pack 1 (SP1). Limits over 4 GB for 32-bit Windows assume that PAE is enabled.

VersionLimit on X86Limit on X64Limit on IA64
Windows Server 2003 with Service Pack 1 (SP1), Datacenter Edition64 GB
(16 GB with 4GT)
X64 1 TB1 TB
Windows Server 2003 with Service Pack 1 (SP1), Enterprise Edition64 GB
(16 GB with 4GT)
X64 1 TB1 TB
Windows Server 2003 with Service Pack 1 (SP1), Standard Edition4 GB32 GB 

 

Physical Memory Limits: Windows Server 2003

The following table specifies the limits on physical memory for Windows Server 2003. Limits over 4 GB for 32-bit Windows assume that PAE is enabled.

VersionLimit on X86Limit on IA64
Windows Server 2003, Datacenter Edition64 GB
(16 GB with 4GT)
512 GB
Windows Server 2003, Enterprise Edition64 GB
(16 GB with 4GT)
512 GB
Windows Server 2003, Standard Edition4 GB 
Windows Server 2003, Web Edition2 GB 
Windows Small Business Server 20034 GB 
Windows Compute Cluster Server 2003 32 GB
Windows Storage Server 2003, Enterprise Edition8 GB 
Windows Storage Server 20034 GB 

 

Physical Memory Limits: Windows XP

The following table specifies the limits on physical memory for Windows XP.

VersionLimit on X86Limit on X64Limit on IA64
Windows XP4 GB128 GB128 GB (not supported)
Windows XP Starter Edition512 MBN/AN/A

 

Physical Memory Limits: Windows Embedded

The following table specifies the limits on physical memory for Windows Embedded.

VersionLimit on X86Limit on X64
Windows XP Embedded4 GB 
Windows Embedded Standard 20094 GB 
Windows Embedded Standard 74 GB192 GB

 

How graphics cards and other devices affect memory limits

Devices have to map their memory below 4 GB for compatibility with non-PAE-aware Windows releases. Therefore, if the system has 4GB of RAM, some of it is either disabled or is remapped above 4GB by the BIOS. If the memory is remapped, X64 Windows can use this memory. X86 client versions of Windows don’t support physical memory above the 4GB mark, so they can’t access these remapped regions. Any X64 Windows or X86 Server release can.

X86 client versions with PAE enabled do have a usable 37-bit (128 GB) physical address space. The limit that these versions impose is the highest permitted physical RAM address, not the size of the IO space. That means PAE-aware drivers can actually use physical space above 4 GB if they want. For example, drivers could map the "lost" memory regions located above 4 GB and expose this memory as a RAM disk.

4-Gigabyte Tuning

IMAGE_FILE_LARGE_ADDRESS_AWARE

Physical Address Extension

 

 

  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
当一个容器被YARN杀死时,是因为它超出了已分配给它的内存限制。在这种情况下,容器的使用内存为54.2G,而给定的物理内存限制为53G。 YARN是用于在Apache Hadoop集群上进行作业调度和资源管理的框架。它负责为容器分配所需的资源,例如内存和CPU。每个容器都有一个分配给它的内存限制,以确保集群中的资源可以按照计划分配和使用。 当容器使用的内存超过了分配给它的限制时,YARN会将其标记为超出内存限制,并杀死容器。这是为了防止容器继续使用过多的资源,从而导致集群中的其他作业受到影响。 要解决这个问题,有几种可能的方法。首先,可以检查作业的配置,确保容器被分配了足够的内存来执行其任务。如果容器的任务确实需要大量的内存,那么可以增加集群中的可用内存量,或者减少其他作业的内存需求,以便为该容器提供更多的资源。 此外,还可以尝试优化作业以减少其内存使用量。这可能包括使用更高效的算法或数据结构,或者优化代码以减少不必要的内存分配。通过这些方法,可以减少容器使用的内存量,并避免超出内存限制而被YARN杀死。 总之,当一个容器被YARN杀死因为超出内存限制时,需要检查作业的配置和资源分配,以及尝试优化作业以减少内存使用。这样可以避免类似的问题,并确保作业能够在分配的资源范围内正常运行。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值