解决了

CVM资源

  • 2016年3月29日
  • 9回复
  • 2056年观点
B.
徽章 +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.55:Fail：CVM存储器16433468 KB小于阈值24 GBNODE 10.0.0.57:Fail：CVM存储器16433468 KB小于阈值24 GBNODE 10.0.0.56:FAIL：CVM存储器16433468 KB小于阈值24 Gbrefer到KB 1513，有关LDAP_CONFIG_CHECK的详细信息，请参见LDAP_CONFIG_CHECK的详细信息：节点10.0.0.56:2INFO：NO LDAP CONFIG.REFER到KB 2997了解详情ldap_config_checkdetailed for cvm_numa_configuration_check：node 10.0.0.58 :info：cvm上的vcpus（8）的数量超过max核心（6）per numa node.node 10.0.0.55 :info：CVM上的VCPU（8）数量超过MAX核心（6）Per Numa node.node 10.0.0.57 :info：CVM上的VCPU（8）的数量超过MAX核心（6）Per Numa node.node 10.0.0.56 :info：numberCVM上的VCPU（8）超过MAX核心（6）每个NUMA node。有关CVM_NUMA_CONFIGURATY_CHECKDETAILED INFIMIT的详细信息，请访问KB 3034vm_checks的ion：我把一切都从戴尔留下了默认值。我想到了关于这个配置的戴尔，但我以为我可能更愿意从马的嘴里听到它。

1.这些是6个核心处理器，因此CVM不会更好地配置为6VCPU？这样他们就不必等待6个核心和2个从下一个处理器等待指导？

2.此集群的最佳内存设置可能是什么？这是一些设置：

  • 复制因子2.
  • 压缩
  • 压缩延迟0分钟。
  • 压缩空间保存1.3 TIB
  • 压缩比1.53：1
  • 性能层重复数据删除
  • 在磁盘重复数据删除
  • 保存磁盘DEDUP空间 -
  • 磁盘代码比率1：1
图标

最好的答案j2016年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"}">
查看原版
    \n
    \nPer Host:
    \n
      \n
    • 2 x Xeon CPU E5-2620 v3 @ 2.40GHz \n
    • 256GB RAM \n
    • 4.4 TB of storage 400GB of which is SSD<\/ul>we got this error after running the NCC checks:
      \n
      \nNode 10.0.0.58:FAIL: CVM memory 16433468 kB is less than the threshold 24 GBNode 10.0.0.55:FAIL: CVM memory 16433468 kB is less than the threshold 24 GBNode 10.0.0.57:FAIL: CVM memory 16433468 kB is less than the threshold 24 GBNode 10.0.0.56:FAIL: CVM memory 16433468 kB is less than the threshold 24 GBRefer to KB 1513 for details on cvm_memory_checkDetailed information for ldap_config_check:Node 10.0.0.56:INFO: No ldap config is specified.Refer to KB 2997 for details on ldap_config_checkDetailed information for cvm_numa_configuration_check:Node 10.0.0.58:INFO: Number of vCPUs(8)on the CVM is more than the max cores(6) per NUMA node.Node 10.0.0.55:INFO: Number of vCPUs(8)on the CVM is more than the max cores(6) per NUMA node.Node 10.0.0.57:INFO: Number of vCPUs(8)on the CVM is more than the max cores(6) per NUMA node.Node 10.0.0.56:INFO: Number of vCPUs(8)on the CVM is more than the max cores(6) per NUMA node.Refer to KB 3034 for details on cvm_numa_configuration_checkDetailed information for vm_checks:I left everything as default from Dell. I thought about calling Dell about this config, but I thought I might prefer to hear it from the horse's mouth.
      \n
      \n1. these are 6-core processors, so wouldn't the CVM's be better configured for 6vCPU's? so that they don't have to wait on 6 cores and 2 from the next processor to do instruction?
      \n
      \n2. What might be the optimum memory settings for this Cluster? here's some settings:
      \n
      \n
        \n
      • Replication Factor 2 \n
      • Compression On \n
      • Compression Delay 0 Min. \n
      • Compression Space Saved 1.3 TiB \n
      • Compression Ratio 1.53 : 1 \n
      • Performance Tier Deduplication On \n
      • On Disk Deduplication Off \n
      • On Disk Dedup Space Saved - \n
      • On Disk Dedup Ratio 1 : 1<\/ul>","quoteUsername":"bpr-admin","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

    9回复

    B.
    UserLevel 4.
    徽章 +17
    默认CVM配置使用8 VCPU和16GB内存

    NCC将根据Nutanix的最佳实践运行以告知集群状况
    随着压缩和副品，更好地将24GB分配给CVM
    \n
    \nNCC will run per Nutanix best practice to inform cluster condition
    \nAs Compress and Dedupe is on, better assign 24GB to the CVM","quoteUsername":"bezeddin","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    B.
    徽章 +7
    我很好奇Nutanix可能会做些什么来优化Hexa核心处理器。但是，我明白默认值为8 VCPU。问题是关于系统优化。有没有见解？
    B.
    UserLevel 4.
    徽章 +17
    虚拟处理器调度算法将优化CVM上的CPU利用率
    cvm就像在虚拟机管理程序上运行的VM
    CPU核心利用动态变化一直变化
    \nCVM just like VM running on Hypervisor
    \nCPU core utilization dynamically change all the time","quoteUsername":"bezeddin","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    j
    秩
    UserLevel 6.
    徽章 +29
    嗨，谢谢你伸出援手。

    我会在这里添加一点颜色

    记忆
    NCC是标记内存，因为您已获得Perf-Tier Dedupe，建议每个主机拥有24GB的CVM内存。

    内联压缩很棒，只需要16GB内存，所以没有担心那里。

    重新CPU
    超级，超级，超长的故事，电梯版本是，对于最长的时间来说，我们的“默认”已经是8 VCPU CVM，但我们不保留所有8个VCPU的，因此管理程序调度程序将与“用户”VM（服务器）一起优先考虑， ETC）。

    NCC检查实际上是由我部分驱动的，而且坦率地说，它超越了我们想要的门。未来的NCC释放（可能是2.2.2，很快出来）将禁用此检查以防止在现场混淆。

    也就是说，前进，未来，未来的NCC / NOS发布将执行以下操作
    重新打开
    基于硬件平台对CVM尺寸进行适当的指导
    “新建”映像的默认值将考虑这些指导，因此它将从新系统上的跳转将是好的。当然，现有系统需要一点调整。



    底线：要么关闭perf tier dedupe，要摆脱第一个警告（或增加CVM到24g），并忽略现在的CVM NUMA检查，直到新的指导出现
    Jon Kohler |技术总监，工程，Nutanix |Nutanix NPX＃003，VCDX＃116 |@jonkohler |如果有用，请荣誉！
    \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","quoteUsername":"Jon","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    B.
    徽章 +7
    我有很多记忆，所以我将把它带到24 GB。

    但是，在看到NUMA检查之前，我认为在处理器为6核的系统上需要CVM需要8VCPU奇数。我的VMware的肤色是，为了传递给CPU的指令，需要提供8个核心，直到它们是VM必须等待。我在这种理解中不正确吗？
    \n
    \nHowever, before ever seeing the NUMA check, I did think it odd to have the CVM require 8vCPU on a system where the processors are 6-core. My understanind of VMware is that in order for an instruction to pass to the CPU, 8 cores would need to be available, and that until they are the VM has to wait. Am I incorrect in this understanding?","quoteUsername":"bpr-admin","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    j
    秩
    UserLevel 6.
    徽章 +29
    您正在考虑共同调度和共同停止，这与5.5和6.0中的问题实际上并不大于ESX 3.x天。


    这里的问题是“Numa宽度”而不是共同停止，这少于CPU调度问题，并且在理论上，您可以在理论上具有CPU线程在处理器之间跨QPI寻址内存的CPU线程不是死刑，它只是不太理想。

    所有这些Numa的东西都是关于尽可能优化。您现在可以很好地完成配置，在我们最终确定一些工程和QA努力之后，您可能会在将来的占用空间较小的努力之后看到未来发布后的指导发生变化，这应该解决6个核心系统上的NUMA宽度。
    Jon Kohler |技术总监，工程，Nutanix |Nutanix NPX＃003，VCDX＃116 |@jonkohler |如果有用，请荣誉！
    \n
    \n
    \nthe issue here is \"NUMA width\" rather than co-stop, which is less of an CPU scheduling issue, and more of a memory scheduling issue, where you could, in theory, have CPU threads addressing memory across the QPI between processors, which isn't a death sentence, its just less than ideal.
    \n
    \nAll of this NUMA stuff is all about optimizing as much as possible. You'll be fine with your config now,<\/b> and you'll likely see a change in guidance after a future release, after we finalize some engineering and QA efforts on making the footprint smaller, which should address NUMA width on 6 core systems.","quoteUsername":"Jon","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    B.
    徽章 +7
    谢谢，这是非常有用的信息！
    B.
    徽章 +7
    有一个问题：

    我即将开始将24GB申请到CVM的内存大小，但是，当我查看Active RAM时，CVM都是在4或5 GB的范围内。24GB真的是最好的吗？
    \n
    \nI was about to start applying 24GB to the memory sizes of the CVM however, when I looked at Active RAM the CVM's are all either in the 4 or 5 GB range. Is 24GB really the best?","quoteUsername":"bpr-admin","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    j
    秩
    UserLevel 6.
    徽章 +29
    活动内存将取决于您驾驶工作负载的努力。现在可能不会很高，但在更高的利用率期间，随着您添加更多工作量和需求，它将上升。

    过去，请记住，我们将尽可能完整地保持内存，以通过保持尽可能多的数据来促进缓存命中。
    Jon Kohler |技术总监，工程，Nutanix |Nutanix NPX＃003，VCDX＃116 |@jonkohler |如果有用，请荣誉！
    \n
    \nPast that, Keep in mind that we'll keep that memory as full as possible, to promote cache hits by keeping as much data in there as possible.","quoteUsername":"Jon","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

    回复


    条款和条件
    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