You can use the advanced NUMA attributes to customize NUMA usage.
|Numa.RebalancePeriod||Controls the frequency of rebalance periods, specified in milliseconds. More frequent rebalancing can increase CPU overheads, particularly on machines with a large number of running virtual machines. More frequent rebalancing can also improve fairness.||2000|
|Numa.MigImbalanceThreshold||The NUMA rebalancer computes the CPU imbalance between nodes, accounting for the difference between each virtual machine’s CPU time entitlement and its actual consumption. This option controls the minimum load imbalance between nodes needed to trigger a virtual machine migration, in percent.||10|
|Numa.RebalanceEnable||Activate NUMA rebalancing and scheduling. Set this option to 0 to deactivate all NUMA rebalancing and initial placement of virtual machines, effectively deactivating the NUMA scheduling system.||1|
|Numa.RebalanceCoresTotal||Specifies the minimum number of total processor cores on the host required to activate the NUMA rebalancer.||4|
Specifies the minimum number of processor cores per node required to activate the NUMA rebalancer.
This option and Numa.RebalanceCoresTotal are useful when deactivating NUMA rebalancing on small NUMA configurations (for example, two-way Opteron hosts), where the small number of total or per-node processors can compromise scheduling fairness when you activate NUMA rebalancing.
|Numa.AutoMemAffinity||Automatically set memory affinity for virtual machines that have CPU affinity set.||1|
|Numa.PageMigEnable||Automatically migrate pages between NUMA nodes to improve memory locality. Page migration rates set manually are still in effect.||1|