In ESX 3.5, the CPU scheduler logically partitions a host's physical CPU into cells, by default, there are 4 cores per cell for scalability reason. The scheduler can make decision locally within a cell without affecting other cells. However, with the introduction of 6 cores CPU, this may lead into some cell span sockets. You might experience performance issue when VMs are using those cells. If you are using those CPUs. You can change it from both VIclient and command line.
From the command line interface (on classic ESX):
1.Enter:
esxcfg-advcfg --set-kernel 6 cpuCellSize
2. Reboot the ESX host.
From the remote command line interface (on ESXi):
1.Enter:
vicfg-advcfg --set-kernel 6 cpuCellSize
2. Reboot the ESX host.
Note: ESX 4.0 uses per-pCPU locks instead of cell scheduler. You will not see the span socket performance issue on ESX 4.0
- Select the Configuration tab in the VI client.
- Select Advanced Settings.
- Select VMkernel.
- In the right pane, locate VMkernel.Boot.cpuCellSize .
- Change the value to 6 .
From the command line interface (on classic ESX):
1.Enter:
esxcfg-advcfg --set-kernel 6 cpuCellSize
2. Reboot the ESX host.
From the remote command line interface (on ESXi):
1.Enter:
vicfg-advcfg --set-kernel 6 cpuCellSize
2. Reboot the ESX host.
Note: ESX 4.0 uses per-pCPU locks instead of cell scheduler. You will not see the span socket performance issue on ESX 4.0
Post a Comment