Hmmm, perhaps I responded a bit too quickly, as there can be some performance benefit to pinning to a specific NUMA node (CPU socket). Particularly if our VMs were only running with only four vCPUs each.
So to qualify my statement: Given the configuration we’re running - VMs with eight vCPUs/each, along with significant CPU overcommitment - I wouldn’t recommend using pinning. > On 2021-05-17-M, at 18:26, Christopher Nielsen <[email protected]> > wrote: > > We don’t want any type of pinning, as that will further exacerbate the > situation. > >> On 2021-05-17-M, at 18:24, Ryan Schmidt <[email protected]> wrote: >> >>> On May 17, 2021, at 13:13, Jason Liu wrote: >>> >>> Regarding CPU overcommitment: Are the virtual hosts doing any sort of CPU >>> pinning? Many virtualization products have the ability to specify which of >>> the pCPU cores a guest is allowed to use. As far as I can remember, >>> products like KVM and ESXi can do CPU pinning, while VirtualBox cannot. >> >> Nope, nothing like that is set up. Is there any reason why we would want >> that?
