[转载]Memory Limits for Windows and Windows Server Releases
Memory Limits for Windows and Windows Server Releases
This topic describes the memory limits for supported Windows and Windows Server releases.
- Memory and Address Space Limits
- Physical Memory Limits: Windows 10
- Physical Memory Limits: Windows 8
- Physical Memory Limits: Windows Server 2012
- Physical Memory Limits: Windows 7
- Physical Memory Limits: Windows Server 2008 R2
- Physical Memory Limits: Windows Server 2008
- Physical Memory Limits: Windows Vista
- Physical Memory Limits: Windows Home Server
- Physical Memory Limits: Windows Server 2003 R2
- Physical Memory Limits: Windows Server 2003 with Service Pack 2 (SP2)
- Physical Memory Limits: Windows Server 2003 with Service Pack 1 (SP1)
- Physical Memory Limits: Windows Server 2003
- Physical Memory Limits: Windows XP
- Physical Memory Limits: Windows Embedded
- How graphics cards and other devices affect memory limits
- Related topics
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 type | Limit on X86 | Limit in 64-bit Windows |
|---|---|---|
|
User-mode virtual address space for each 32-bit process |
2 GB Up to 3 GB with IMAGE_FILE_LARGE_ADDRESS_AWARE and 4GT |
2 GB withIMAGE_FILE_LARGE_ADDRESS_AWARE cleared (default) 4 GB withIMAGE_FILE_LARGE_ADDRESS_AWARE set |
|
User-mode virtual address space for each 64-bit process |
Not applicable |
With 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 withIMAGE_FILE_LARGE_ADDRESS_AWARE cleared |
|
Kernel-mode virtual address space |
2 GB From 1 GB to a maximum of 2 GB with 4GT |
8 TB Windows 8.1 and Windows Server 2012 R2: 128 TB |
|
Paged pool |
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: 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 pool |
75% 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 theSystemCacheLimit 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.
| Version | Limit on X86 | Limit on X64 |
|---|---|---|
| Windows 10 Enterprise |
4 GB |
2TB |
| Windows 10 Education |
4 GB |
2TB |
| Windows 10 Pro |
4 GB |
2TB |
| Windows 10 Home |
4 GB |
128GB |
Physical Memory Limits: Windows 8
The following table specifies the limits on physical memory for Windows 8.
| Version | Limit on X86 | Limit on X64 |
|---|---|---|
| Windows 8 Enterprise |
4 GB |
512 GB |
| Windows 8 Professional |
4 GB |
512 GB |
| Windows 8 |
4 GB |
128 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.
| Version | Limit on X64 |
|---|---|
| Windows Server 2012 Datacenter |
4 TB |
| Windows Server 2012 Standard |
4 TB |
| Windows Server 2012 Essentials |
64 GB |
| Windows Server 2012 Foundation |
32 GB |
| Windows Storage Server 2012 Workgroup |
32 GB |
| Windows Storage Server 2012 Standard |
4 TB |
| Hyper-V Server 2012 |
4 TB |
Physical Memory Limits: Windows 7
The following table specifies the limits on physical memory for Windows 7.
| Version | Limit on X86 | Limit on X64 |
|---|---|---|
| Windows 7 Ultimate |
4 GB |
192 GB |
| Windows 7 Enterprise |
4 GB |
192 GB |
| Windows 7 Professional |
4 GB |
192 GB |
| Windows 7 Home Premium |
4 GB |
16 GB |
| Windows 7 Home Basic |
4 GB |
8 GB |
| Windows 7 Starter |
2 GB |
N/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.
| Version | Limit on X64 | Limit on IA64 |
|---|---|---|
| Windows Server 2008 R2 Datacenter |
2 TB |
|
| Windows Server 2008 R2 Enterprise |
2 TB |
|
| Windows Server 2008 R2 for Itanium-Based Systems |
|
2 TB |
| Windows Server 2008 R2 Foundation |
8 GB |
|
| Windows Server 2008 R2 Standard |
32 GB |
|
| Windows HPC Server 2008 R2 |
128 GB |
|
| Windows Web Server 2008 R2 |
32 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.
| Version | Limit on X86 | Limit on X64 | Limit on IA64 |
|---|---|---|---|
| Windows Server 2008 Datacenter |
64 GB |
1 TB |
|
| Windows Server 2008 Enterprise |
64 GB |
1 TB |
|
| Windows Server 2008 HPC Edition |
|
128 GB |
|
| Windows Server 2008 Standard |
4 GB |
32 GB |
|
| Windows Server 2008 for Itanium-Based Systems |
|
|
2 TB |
| Windows Small Business Server 2008 |
4 GB |
32 GB |
|
| Windows Web Server 2008 |
4 GB |
32 GB |
|
Physical Memory Limits: Windows Vista
The following table specifies the limits on physical memory for Windows Vista.
| Version | Limit on X86 | Limit on X64 |
|---|---|---|
| Windows Vista Ultimate |
4 GB |
128 GB |
| Windows Vista Enterprise |
4 GB |
128 GB |
| Windows Vista Business |
4 GB |
128 GB |
| Windows Vista Home Premium |
4 GB |
16 GB |
| Windows Vista Home Basic |
4 GB |
8 GB |
| Windows Vista Starter |
1 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 thatPAE is enabled.
| Version | Limit on X86 | Limit on X64 |
|---|---|---|
|
Windows Server 2003 R2 Datacenter Edition |
64 GB (16 GB with 4GT) |
1 TB |
|
Windows Server 2003 R2 Enterprise Edition |
64 GB (16 GB with 4GT) |
1 TB |
|
Windows Server 2003 R2 Standard Edition |
4 GB |
32 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.
| Version | Limit on X86 | Limit on X64 | Limit on IA64 |
|---|---|---|---|
|
Windows Server 2003 with Service Pack 2 (SP2), Datacenter Edition |
64 GB (16 GB with 4GT) |
1 TB |
2 TB |
|
Windows Server 2003 with Service Pack 2 (SP2), Enterprise Edition |
64 GB (16 GB with 4GT) |
1 TB |
2 TB |
|
Windows Server 2003 with Service Pack 2 (SP2), Standard Edition |
4 GB |
32 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.
| Version | Limit on X86 | Limit on X64 | Limit on IA64 |
|---|---|---|---|
|
Windows Server 2003 with Service Pack 1 (SP1), Datacenter Edition |
64 GB (16 GB with 4GT) |
X64 1 TB |
1 TB |
|
Windows Server 2003 with Service Pack 1 (SP1), Enterprise Edition |
64 GB (16 GB with 4GT) |
X64 1 TB |
1 TB |
|
Windows Server 2003 with Service Pack 1 (SP1), Standard Edition |
4 GB |
32 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 PAEis enabled.
| Version | Limit on X86 | Limit on IA64 |
|---|---|---|
|
Windows Server 2003, Datacenter Edition |
64 GB (16 GB with 4GT) |
512 GB |
|
Windows Server 2003, Enterprise Edition |
64 GB (16 GB with 4GT) |
512 GB |
|
Windows Server 2003, Standard Edition |
4 GB |
|
|
Windows Server 2003, Web Edition |
2 GB |
|
|
Windows Small Business Server 2003 |
4 GB |
|
|
Windows Compute Cluster Server 2003 |
|
32 GB |
|
Windows Storage Server 2003, Enterprise Edition |
8 GB |
|
|
Windows Storage Server 2003 |
4 GB |
|
Physical Memory Limits: Windows XP
The following table specifies the limits on physical memory for Windows XP.
| Version | Limit on X86 | Limit on X64 | Limit on IA64 |
|---|---|---|---|
| Windows XP |
4 GB |
128 GB |
128 GB (not supported) |
| Windows XP Starter Edition |
512 MB |
N/A |
N/A |
Physical Memory Limits: Windows Embedded
The following table specifies the limits on physical memory for Windows Embedded.
| Version | Limit on X86 | Limit on X64 |
|---|---|---|
|
Windows XP Embedded |
4 GB |
|
|
Windows Embedded Standard 2009 |
4 GB |
|
|
Windows Embedded Standard 7 |
4 GB |
192 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.
Related topics
4-Gigabyte TuningIMAGE_FILE_LARGE_ADDRESS_AWAREPhysical Address Extension
Community Additions
[转载]Memory Limits for Windows and Windows Server Releases的更多相关文章
- Memory Limits for Windows and Windows Server Releases
来源:https://msdn.microsoft.com/en-us/library/windows/desktop/aa366778(v=vs.85).aspx Limits on memory ...
- How to detect, enable and disable SMBv1, SMBv2, and SMBv3 in Windows and Windows Server
转自:https://support.microsoft.com/en-us/help/2696547/detect-enable-disable-smbv1-smbv2-smbv3-in-windo ...
- windows上zend server安装 报The server encountered an internal error or misconfiguration and was unable to complete your request -解决方法 摘自网络
windows上zend server安装完成后报如下错误: Internal Server Error The server encountered an internal error or m ...
- 从Windows迁移SQL Server到Linux
前一篇博客关于SQL Server on Linux的安装,地址:http://www.cnblogs.com/fishparadise/p/8057650.html,现在测试把Windows平台下的 ...
- Net 4.5 WebSocket 在 Windows 7， Windows 8 and Server 2012上的比较以及问题
Net 4.5 WebSocket在Windows 8, Windows 10, Windows Server 2012可以,但是在Windows 7, 就会报错. 错误1.“一个文件正在被访问,当前 ...
- Net 4.5 WebSocket 在 Windows 7， Windows 8 and Server 2012上的比较
.Net 4.5 WebSocket Server Running on Windows 7? Net 4.5 WebSocket Server 可以运行在 Windows 7,但是Net 4.5的 ...
- Windows 2008 R2 Server FTP使用问题
Windows 2008 R2 Server FTP必须在安装IIS的时候.安装IIS6.0兼职性. 否则建的FTP网站仅仅有关了防火墙才干使用. 原因未知.
- Install MongoDB on Windows （Windows下安装MongoDB）
Install MongoDB on Windows Overview Use this tutorial to install MongoDB on a Windows systems. PLATF ...
- [hadoop] - Container [xxxx] is running beyond physical/virtual memory limits.
当运行mapreduce的时候,有时候会出现异常信息,提示物理内存或者虚拟内存超出限制,默认情况下:虚拟内存是物理内存的2.1倍.异常信息类似如下: Container [pid=13026,cont ...
随机推荐
- 在H5页面内通过地址调起高德地图实现导航
项目中用到的一个功能是要通过点击地址来实现打开地图app实现地址导航. 如下图: 实现思路就是在H5页面内通过点击marker图标然后进行当前位置与页面上地址的路程规划与导航. 由于项目中用到的是高德 ...
- 在 Server 2008 企业版下， 安装 IIS 7 后，勾选好 请求筛选模块了。安装完毕后，"请求筛选"却不显示!
下载并安装 Administration Pack 到你的Windows Server 2008 上.可以通过下面的链接来下载Administration Pack. https://www.iis. ...
- js == 与 === 的区别[转]
we文章转自http://blog.sina.com.cn/s/blog_4b32835b01014iv9.html 1.对于string,number等基础类型,==和===是有区别的 1)不同类型 ...
- 深入浅出的webpack构建工具---webpack3版本的CommonsChunkPlugin详解(六)
阅读目录 一:什么是CommonsChunkPlugin, 它的作用是什么? 二:webpack3中CommonsChunkPlugin配置项及含义? 回到顶部 一:什么是CommonsChunkPl ...
- JAVA 第九周学习总结
20175308 2018-2019-2 <Java程序设计>第九周学习总结 教材学习内容总结 准备工作 下载MYSQL数据库管理系统 前往MYSQL官网的下载页面,选择相应平台的MYSQ ...
- FreeRTOS的任务非运行态
当FreeRTOS启动任务调度器以后,任务调度器会在心跳中断函数中确定下一个要运行的任务,如果任务调度器仅仅依靠任务优先级来判断该运行哪个任务,这样会造成低优先级的任务根本没法运行,因为FreeRTO ...
- ASP.NET Core 释放 IDisposable 对象的四种方法
本文翻译自<Four ways to dispose IDisposables in ASP.NET Core>,由于水平有限,故无法保证翻译完全正确,欢迎指出错误.谢谢! IDispos ...
- 坑爹的InetAddress getLocalHost函数
今天在跑dubbo 的 DemoService 2.5.4-SNAPSHOT版本的时候,遇到到一个奇怪的问题.consumer怎么都连接不上provider的服务.最后才发现是由于dubbo自 己实现 ...
- 算法相关——Java排序算法之快速排序（三）
0. 前言 本系列文章将介绍一些常用的排序算法.排序是一个非常常见的应用场景,也是开发岗位面试必问的一道面试题,有人说,如果一个企业招聘开发人员的题目中没有排序算法题,那说明这个企业不是一个" ...
- 使用Hexo+Github搭建属于自己的博客（基础）
前言 hexo是一个台湾人做的基于Node.js的静态博客程序,优势是生成静态文件的速度非常快,支持markdown, 我最终选定它的原因是它速度快而且不容易出错,并且可以一键部署到github或者其 ...