![]() ![]() Now we can input the details into my vSphere Cluster Sizing Calculator and work out the overcommitment including our desired availability level (in my case, N+1) and we get the following: So we have our 3 node cluster with 60 physical cores (pCores) and we have provisioned 130 vCPUs. This can be found on the “VMs” page in PRISM as shown below. Next we need to find out how many vCPUs we’ve provisioned in the cluster. In my example, I have three nodes, each with 20 cores for a total of 60 physical cores. Then simply add up the total number of physical cores in the cluster. ![]() If you have multiple node types in your cluster, repeat this step for each different node type in your cluster. In this case we have 2 sockets and 20 cores total for a total of 10 physical cores per socket. Once you’ve done that you will see below in the “Summary” section the CPU Model, No. With Nutanix this is very easy to work out, first goto the Hardware page in PRISM and click Diagram, then select one of your nodes as shown below. Let’s start with “How much overcommitment do I have now?”. “How do I know if overcommitment is causing a performance problem?”. The answer is of course “It depends” and there are many factors including but not limited to, workload type, physical CPUs and how complimentary the workloads (other VMs) are. Question: “How much CPU overcommitment is ok?”. Help! My performance is terrible and my consultant/vendor says it’s due to high/excessive CPU overcommitment! What do I do next? ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |