Hi,
Please check the following docs:
Processor Compatibility Mode in Hyper-V
If you plan to move virtual machines, without rebooting them, between virtualization hosts that may use different generations of processors, you should enable processor compatibility mode. For example, you would enable processor compatibility mode to ensure that you can live migrate your virtual machines between cluster nodes that use different processor feature sets. You could also use processor compatibility mode to save a virtual machine and restore it on a host computer that has a different processor feature set than the source host.
Performance Impact of Hyper-V CPU Compatibility Mode
Planning Failover Cluster Node Sizing
So let’s say you have 1,000 VMs… if you have a single 32-node cluster, and the entire cluster goes down, that means all 1,000 VMs go down. Where if you had them broken into two 16-node clusters, then only 500 VMs (half) go down. Defining fault domains can protect you from cluster class failures.
The larger the cluster, the more nodes Dynamic Optimization has to work with and the better balancing it can achieve. So while creating multiple smaller clusters may divide up multiple fault domains, creating too small of clusters can increase the management and keep them from being utilized optimally. Defining a larger cluster creates finer granularity to spread and move across.
Thanks for your time!
Best Regards,
Mico Mi
-----------------------------
If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.