CPU core count seems to be wrong

[Daxcor]

When I look at the dashboard it reports:

72 x Intel(R) Xeon(R) CPU E5-2697 v4 @ 2.30GHz (2 Sockets)

What is physically installed:

28 Intel(R) Xeon(R) CPU E5-2697 v4 @ 2.60GHz (2 Sockets)

Why would these be different?
Version 8.0.3

Thank
Brad

 

[leesteken]

When I look at the dashboard it reports:

72 x Intel(R) Xeon(R) CPU E5-2697 v4 @ 2.30GHz (2 Sockets)

Two CPUs with each 18 cores with hyper-threads is 2x18x2 = 72. There are 72 execution units and the identification reported by each CPU is "Intel(R) Xeon(R) CPU E5-2697 v4 @ 2.30GHz". That results in "72 x Intel(R) Xeon(R) CPU E5-2697 v4 @ 2.30GHz (2 Sockets)".

What is physically installed:

28 Intel(R) Xeon(R) CPU E5-2697 v4 @ 2.60GHz (2 Sockets)

Where did you get the 28 from? 18 cores with hyper-threading is 36 threads: https://www.intel.com/content/www/u...697-v4-45m-cache-2-30-ghz/specifications.html

 

[Daxcor]

Humm ok, it came from the invoice, but it could be wrong, I will check the machine. It was the hyperthreading part that I didn't understand. so when I am assigning cpus to a vm, am I assigning a real core or a hyper thread?

 

[leesteken]

Humm ok, it came from the invoice, but it could be wrong, I will check the machine.

Could be a typo (hitting 2 instead of 1).

It was the hyperthreading part that I didn't understand. so when I am assigning cpus to a vm, am I assigning a real core or a hyper thread?

You are not binding to any core or thread or socket in particular. The Linux kernel will schedule the virtual CPUs over (the same number of) real threads (and cores and sockets).
Please be aware that the extra thread per code only gives between 5% and 25% extra performance (on a fully loaded system).

Since you have two sockets, you probably have a NUMA system and it might be worthwhile to give each VM also two virtual sockets and enable the NUMA option (so the VM knows which memory is connected to which socket).