Hi Everyone,
I just setup a replication between 2 Hyper-V Hosts. The source host has 16 cores per CPU and the destination host has only 12 cores per CPU.
So the settings of that VM on the source host says 16 processors per NUMA which is correct but I can see that this setting is not changed on the destination host. So this differs from the native settings that host has usually (max 12 processors per NUMA).
Is that something i should change?
-
- Lurker
- Posts: 1
- Liked: never
- Joined: Nov 15, 2021 10:41 am
- Full Name: Daniel Huebner
- Contact:
-
- Product Manager
- Posts: 14844
- Liked: 3086 times
- Joined: Sep 01, 2014 11:46 am
- Full Name: Hannes Kasparick
- Location: Austria
- Contact:
Re: Replication to different core count
Hello,
and welcome to the forums.
I would always try to fit a VM into one NUMA node. As an alternative, virtual NUMA could be used.
Whether you "should" change, can probably only be answered by a benchmark test.
Best regards,
Hannes
and welcome to the forums.
I would always try to fit a VM into one NUMA node. As an alternative, virtual NUMA could be used.
Whether you "should" change, can probably only be answered by a benchmark test.
Best regards,
Hannes
-
- Veteran
- Posts: 528
- Liked: 144 times
- Joined: Aug 20, 2015 9:30 pm
- Contact:
Re: Replication to different core count
If the VM fits within a single NUMA node on the destination host, then the guest NUMA settings make no difference. It also doesn't matter that much if your Hyper-V host has the "Allow VMs to span NUMA nodes" option enabled.
Here's a good deeper dive into how NUMA works with Hyper-V VMs https://www.starwindsoftware.com/blog/a ... a-settings
Here's a good deeper dive into how NUMA works with Hyper-V VMs https://www.starwindsoftware.com/blog/a ... a-settings
Who is online
Users browsing this forum: Amazon [Bot] and 6 guests