VMware Memory and CPU考虑
2012-10-03 19:39
232 查看
Memory Consideration:
A basic rule for sizing is to have between at least 4 GB and 8 GB of RAM per physical core.
1. For an optimized approach, notably for test, development, and preproduction applications, follow this rule:
The sum of memory configured in VMs can be double the physical RAM in the server.
2. For a conservative approach (for sensitive applications), transpose the same amount of memory used in the physical environment to determine the amount of memory required on the ESXi server and then add 10%.
CPU Consideration:
How many VMs can there be per ESXi host server? Globally, capacity planning can be done as follows:
1. Between two and four vCPUs per core for medium loads
2. One vCPU per core for high loads
Example:
A server with 12 cores allows 24 to 48 vCPUs to run. This is equivalent to 24 to 48 VMs configured each with 1 vCPU for medium application loads. For high-activity applications, this represents 12 vCPUs (for instance, 12 VMs with 12 vCPUs, or 3 VMs with 4 vCPUs).
本文出自 “Ilovecat(个人笔记)” 博客,请务必保留此出处http://hj192837.blog.51cto.com/655995/1011939
A basic rule for sizing is to have between at least 4 GB and 8 GB of RAM per physical core.
1. For an optimized approach, notably for test, development, and preproduction applications, follow this rule:
The sum of memory configured in VMs can be double the physical RAM in the server.
2. For a conservative approach (for sensitive applications), transpose the same amount of memory used in the physical environment to determine the amount of memory required on the ESXi server and then add 10%.
CPU Consideration:
How many VMs can there be per ESXi host server? Globally, capacity planning can be done as follows:
1. Between two and four vCPUs per core for medium loads
2. One vCPU per core for high loads
Example:
A server with 12 cores allows 24 to 48 vCPUs to run. This is equivalent to 24 to 48 VMs configured each with 1 vCPU for medium application loads. For high-activity applications, this represents 12 vCPUs (for instance, 12 VMs with 12 vCPUs, or 3 VMs with 4 vCPUs).
本文出自 “Ilovecat(个人笔记)” 博客,请务必保留此出处http://hj192837.blog.51cto.com/655995/1011939
相关文章推荐
- Linux SNMP OID’s for CPU,Memory and Disk Statistics
- Linux SNMP OID’s for CPU,Memory and Disk Statistics
- Find CPU Speed and Memory Size on Solaris
- To get information of cpu and memory in windows os
- Tmux Show CPU Usage And Memory Usage
- Memory Barrier in Compiler and CPU
- mm: iommu: An API to unify IOMMU, CPU and device memory management
- Linux SNMP OID’s for CPU,Memory and Disk Statistics
- How to determine CPU and memory consumption from inside a process
- CPU Overcommitment and Its Impact on SQL Server Performance on VMware
- Memory Barrier in Compiler and CPU
- Understanding System Memory and CPU speeds
- Shell script for logging cpu and memory usage of a Linux process
- CPU-Cache-and-Memory-Ordering
- Codeforces Round #370 (Div. 2) D. Memory and Scores DP
- 脚本获取 app 的 cpu、memory 信息,使用 pychartdir 生成图表
- Advanced Server Virtualization: VMware and Microsoft Platforms in the Virtual Data Center
- libxxx.so has text relocations. This is wasting memory and prevents...解决方案
- Codeforces Round 370 (Div 2) D.Memory and Scores 【前缀和 DP】双人随机数值增减K A比B多的方案数
- Memory Access vs CPU Speed_你真的了解CPU和内存吗?