Thanks
@Angus Jamieson and Bary. Will move this thread to Turbonomic group.
------------------------------
Veeramani Nambi
Offering Manager, GoToMarket - Communities
------------------------------
Original Message:
Sent: Fri October 08, 2021 08:12 AM
From: Angus Jamieson
Subject: vNUMA enabled VMs carries old host configuration while migration occurs - TURBO
Great question! Most Host clusters are made of homogenous hosts meaning that they all have the same NUMA node configurations. VM Moves within such clusters will not impact NUMA optimisations.
Moves of NUMA optimised VMs between heterogenous hosts may have an impact if the physical NUMA nodes are different between the source and target hosts. Where this may be the case it's good practice to set a Turbonomic policy to constrain the VMs to a set of homogenous hosts or manually review such moves.
Resize actions for NUMA optimised VMs should be manually reviewed. Turbonomic acts as the trigger for the resize but changing Sockets may impact the NUMA optimisation, so customers typically review these actions and then manually adjust the Cores per Socket on the VM to match the recommended target vCPU from Turbonomic."
Regards,
Barry Howard, Turbonomic