开启辅助访问

超融合+云计算论坛

 找回密码
 立即注册

QQ登录

只需一步,快速开始

查看: 1754|回复: 2
收起左侧

[架构设计] CVM 虚拟机推荐配置

[复制链接]
发表于 2016-7-9 08:45:59 | 显示全部楼层 |阅读模式

马上注册,结交更多好友,享用更多功能,让你轻松玩转社区。

您需要 登录 才可以下载或查看,没有帐号?立即注册

x

The Nutanix Controller VM has some sizing guidelines that are published in the official documentation, but the majority of the sizing logic is embedded within Foundation (and Phoenix) which is applied during the node deployment process.

As a customer you can ignore this under the guise of “invisible infrastructure”, but as an NPX candidate you need to understand the details.  Be aware that Nutanix is constantly trying to optimise the CVM code to “do more with less” and leverage the CPU features of each new generation of Intel processors.

The Controller VM has the following vCPU settings and Reservations (ESXi only) assigned during deployment:

  • Default: 8 vCPU, 10,000 MHz Reservation
  • NX-1020: 4 vCPU, 7,000 MHz Reservation
  • NX-1050: 8 vCPU, 10,000 MHz Reservation
  • NX-3000: 8 vCPU, 10,000 MHz Reservation
  • NX-6020: 8 vCPU, 10,000 MHz Reservation
  • NX-6035C: 4 vCPU, Reservation not supported (AHV)
  • NX-7000: 8 vCPU, 10,000 MHz Reservation
  • NX-8000: 8 vCPU, 10,000 MHz Reservation
  • NX-9000: 8 vCPU, 10,000 MHz Reservation

The Nutanix Cluster Check has a check to verify your CVM vCPU is correctly sized: “ncc health_checks system_checks cvm_vcpu_reservation_check”.

During the Foundation deployment, you have the option to select 16GB, 24GB or 32GB of RAM for each CVM (depending upon Foundation version, otherwise change it manually).  The following guide-lines apply to RAM selection:

  • 16GB RAM: Default, minimum configuration
  • 24GB RAM: Performance-tier Deduplication configured for a container
  • 32GB RAM: Capacity-tier Deduplication configured for a container or Business Critical Applications are running in the cluster (greater cache size for databases and MS Exchange)
  • Greater than 32GB RAM: This is a rare requirement for some medical applications that require very large cache sizes (certification process in progress) and “pre-4.5” (before the Extent and Content Caches were unified) it was also used for large business critical databases.

Keep the following in mind when you are customising the vCPU and RAM of Controller VMs in a Nutanix cluster:

  • Consistent, homogeneous cluster-wide settings (keep this in mind when expanding an existing cluster with different hardware models)
  • Fits within the NUMA boundaries of the node and is divisible by the NUMA node
  • Random I/O is CPU bound: more random I/O, increase vCPUs
  • Random reads are less likely to hit the cache
  • Sequential I/O is physical disk bound
  • Sequential reads are more likely to hit the cache
  • If you are exceeding the guidelines, involve Nutanix GSO before putting it into Production.  Deliver supported configurations to your customers.

相关帖子

欢迎来到 【nutanix.club】最大的中文超融合&云计算社区 请记住我们的网址 www.nutanix.club [这是默认签名,更换签名点这里!]
回复

使用道具 举报

发表于 2017-11-22 11:09:55 | 显示全部楼层
8个VCPU和32Gb内存感觉还是有些吃配置
欢迎来到 【nutanix.club】最大的中文超融合&云计算社区 请记住我们的网址 www.nutanix.club [这是默认签名,更换签名点这里!]
回复 支持 反对

使用道具 举报

您需要登录后才可以回帖 登录 | 立即注册

本版积分规则

返回顶部快速回复上一主题下一主题返回列表微信扫一