Author : mimartin
Topic Name : Using CPU Affinity
Publication Name : vSphere Resource Management
Product/Version : VMware vSphere/6.7
do we need to take into consideration that the physical host memory is split into (example:Dell R710) 2 physical CPU in order to correctly configure and attribute cpu cycles. if we have a server that has 64 gig ram per physical CPU, and we setup 2 vm's with each 48gig Ram and 4 vCPU. i would setup the first one with affinity vCPU 0 to 3 and the second one with affinity vCPU 4 to 7... which would represent physical CPU Socket #1... leaving physical CPU Socket #2 free... but from a memory perspective... it would mean that the physical CPU Socket #1 memory would not be enough... will esxi borrow some memory from physical CPU Socket #2 ? when affinity is not used... it is my understanding that esxi will manage the cpu and memory attribution.. but when affinity is into play... i dont know and there is not a lot of info on this...