Join us for a virtual Nutanix User Group meeting with Jarian Gibson as he covers Nutanix Cloud Clusters (NC2) on Azure and AWS with Citrix. <\/span><\/p>

Jarian will take a deep dive into NC2 on Azure architecture and Citrix on NC2 on Azure\u00a0that helps you strengthen your business continuity and disaster recovery position. He\u2019ll also provide the latest updates for NC2 on AWS.<\/span><\/p>

Plus, we're\u00a0giving away a Nutanix suitcase to one lucky winner!\u00a0Opt-in when you register\u00a0to be entered to win.\u00a0<\/p>","author":{"id":113632,"url":"\/members\/karlie-beil-113632","name":"Karlie Beil","avatar":"https:\/\/uploads-us-west-2.insided.com\/nutanix-us\/icon\/200x200\/1581aab3-bcf6-49f4-b2fb-3d11e8c010dc.png","userTitle":"Community Manager","rank":{"isBold":false,"isItalic":false,"isUnderline":false,"name":"Community Manager","color":"#0873ba"},"userLevel":4},"type":"Webinar","url":"https:\/\/next.nutanix.com\/events\/global-nug-nc2-on-azure-and-aws-with-citrix-151","image":"https:\/\/uploads-us-west-2.insided.com\/nutanix-us\/attachment\/f9693b5b-436b-427a-9b98-531b4040ff24_thumb.png","location":"","startsAt":1678298400,"endsAt":1678302000,"contentType":"event","attendees":[],"attendeeCount":0,"isLoggedInUserAttendee":false,"createdAt":"1675974969"},"phrases":{"Forum":{"{n} year|{n} years":"{n} year|{n} years","{n} month|{n} months":"{n} month|{n} months","{n} day|{n} days":"{n} day|{n} days","{n} hour|{n} hours":"{n} hour|{n} hours","{n} minute|{n} minutes":"{n} minute|{n} minutes","just":"just now","{plural} ago":"{plural} ago"}}}">

解决了

CVM资源

  • 2016年3月29日
  • 9回复
  • 2136意见

徽章 +7
我们有一个4主持的戴尔捆绑包。



每个主机:


  • 2 x Xeon CPU E5-2620 V3 @ 2.40GHz
  • 256GB RAM
  • 4.4 TB存储400GB为SSD
运行NCC检查后,我们得到了此错误:



节点10.0.0.58:FAIL:CVM内存16433468 kb小于阈值24 GBNODE 10.0.0.0.55:FAIL:FAIL:CVM内存16433468 KB小于阈值24 GBNODE 24 GBNODE 10.0.0.57:FAIL:FAIL:FAIL:FAIL:CVM MOMEMOR:CVM 16433468 KB BB BBS BLESS24 GBNODE 10.0.0.56:FAIL:CVM内存16433468 kb小于阈值24 GBRefer至KB 1513,以获取有关ldap_config_check的CVM_MEMORY_CHECKDETAILED信息的详细信息,请访问ldap_config_check:noode 10.0.0.56:Info:no ldap inspecied。cvm_numa_configuration_check:node 10.0.0.58:info:cvm上的ldap_config_checkdetailed信息:cvm上的vcpus(8)数量大于max cores(6)per numa numa node.node.node.node 10.0.0.0.0.55:info:大于每个numa节点的最大内核(6)。节点10.0.0.57:info:cvm上的vcpus(8)的数量大于每个numa node.node.node.0.0.0.0.56:inmund:inmumb:number:numa numa node:numa numa numa numa。CVM上的VCPU(8)的最大核心(6)每个numa node.to to kb 3034有关cvm_numa_configuration_checkdetailed Informat的详细信息vm_checks的离子:我将所有内容都留为dell的默认设置。我想到要打电话给戴尔这种配置,但我想我可能更喜欢从马的嘴里听到它。



1.这些是6核处理器,那么6VCPU的CVM是否会更好地配置?这样他们就不必等待下一个处理器的6个内核和2个来进行指导?



2.该集群的最佳内存设置可能是什么?这是一些设置:




  • 复制因子2
  • 压缩
  • 压缩延迟0分钟。
  • 压缩空间保存了1.3 tib
  • 压缩比1.53:1
  • 性能层删除
  • 磁盘重复数据删除
  • 在磁盘上保存空间上 -
  • 在磁盘addup比率1:1
图标

最好的答案乔恩2016年3月31日,11:03

\n
\nI'll add a bit of color here
\n
\nRE Memory
\nNCC is flagging the memory because you've got perf-tier Dedupe on, which is recommended to have 24GB of CVM memory per host for.
\n
\nInline compression is fantastic and only requires 16GB memory, so no worries there.
\n
\nRE CPU's
\nSuper, super, super long story, the elevator version is that for the longest time, our \"default\" has been 8 vCPU CVM's, but we dont RESERVE all 8 vCPU's, so the hypervisor scheduler will prioritize along with \"user\" VM's (servers, etc).
\n
\nThat NCC check was actually partially driven by me, and to be frank, it went out the door sooner than we wanted. a future NCC release (likely 2.2.2, coming out shortly) will disable this check to prevent confusion in the field.
\n
\nThat said, going forward, a future, future NCC\/NOS release will do the following
\nTurn that check back on
\nGive proper guidance on CVM sizing based on the hardware platform
\nDefaults for \"new\" imaging will take these guidances into account, so it will be good from the jump on new systems. Existing systems would need a bit of tweaking of course.
\n
\n
\n
\nBottomline: Either turn off perf tier dedupe to get rid of the first warning (or increase CVM to 24G), and ignore that CVM NUMA check for now, until the new guidance comes out","className":"post__content__best_answer"}">
查看原件

该主题已关闭以供评论

9回复

Userlevel 4
徽章 +17
默认的CVM配置正在使用8 VCPU和16GB内存



NCC将按照Nutanix的最佳实践运行,以告知群集状况

随着压缩和DEDUPE的打开,最好将24GB分配到CVM
徽章 +7
我很好奇Nutanix可能会为Hexa核处理器进行优化。我知道默认值为8 VCPU。问题是关于系统优化。有什么见识吗?
Userlevel 4
徽章 +17
虚拟处理器调度算法将优化CVM上的CPU利用率

CVM就像VM在虚拟机管理程序上运行

CPU核心始终动态更改
UserLevel 6
徽章 +29
嗨,谢谢您的伸出手。



我在这里添加一点颜色



RE内存

NCC正在标记内存,因为您已经启用了perf-tier defupe,建议每个主机的CVM内存24GB。



内联压缩很棒,只需要16GB的内存,因此不用担心。



Re CPU

超级,超级长故事,电梯版本是,在最长的时间内,我们的“默认值”是8个VCPU CVM,但我们不保留所有8个VCPU,因此Hypervisor Scheduler将与“用户” VM一起优先考虑(服务器)(服务器), ETC)。



NCC检查实际上是由我部分驾驶的,坦率地说,它比我们想要的要早。未来的NCC版本(可能很快出现)将禁用此支票,以防止现场混乱。



就是说,展望未来,未来的NCC/NOS发布将执行以下操作

重新打开检查

根据硬件平台对CVM尺寸提供适当的指导

“新”成像的默认值将考虑这些指导,因此从新系统的跳跃中可以很好。现有系统当然需要进行一些调整。







底线:要么关闭Perf Tier Dedupe,以摆脱第一个警告(或将CVM提高到24克),然后忽略CVM Numa检查,直到新指南出现
徽章 +7
我有很多记忆,所以我将其带到24 GB。



但是,在看到NUMA检查之前,我确实认为让CVM在处理器为6核的系统上需要8VCPU是很奇怪的。我对VMware的理解是,为了使指令传递给CPU,需要8个内核,并且直到它们为VM必须等待。我对这种理解不正确吗?
UserLevel 6
徽章 +29
您正在考虑共同开展和共同营业,在5.5和6.0中,这实际上并不比ESX 3.x天的问题大。





这里的问题是“ numa宽度”而不是共同停留,这不是CPU调度问题,而更多的是内存调度问题,从理论上讲,您可以在处理器之间解决QPI的CPU线程,在该问题之间解决该QPI,不是死刑,只是不理想。



所有这些Numa的东西都是尽可能优化的。您现在可以使用config,在将来发行后,您可能会看到指导的变化,在我们完成一些工程和质量检查方面的努力使足迹更小之后,这应该解决6个核心系统上的NUMA宽度。
徽章 +7
谢谢,那是非常有用的信息!
徽章 +7
还有一个问题:



我正要开始将24GB应用于CVM的内存大小,但是,当我查看Active RAM时,CVM都在4或5 GB范围内。24GB真的是最好的吗?
UserLevel 6
徽章 +29
主动内存将取决于您驾驶工作负载的努力。现在可能不是很高,但是在更高利用率的时候,随着您增加更多的工作量和需求,它将上升。



过去,请记住,我们将尽可能保留尽可能充分的记忆,以通过将尽可能多的数据保留在其中。
Learn more about our cookies.<\/a>","cookiepolicy.button":"Accept cookies","cookiepolicy.button.deny":"Deny all","cookiepolicy.link":"Cookie settings","cookiepolicy.modal.title":"Cookie settings","cookiepolicy.modal.content":"We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.<\/a>","cookiepolicy.modal.level1":"Basic
Functional","cookiepolicy.modal.level2":"Normal
Functional + analytics","cookiepolicy.modal.level3":"Complete
Functional + analytics + social media + embedded videos"}}}">
Baidu