No edit summary |
|||
| Line 12: | Line 12: | ||
== Performance Monitoring == | == Performance Monitoring == | ||
Monitor the vCenter appliance resources - you can use the VAMI or ssh into the vCenter appliance and use "vimtop" | Monitor the vCenter appliance resources - you can use the VAMI or ssh into the vCenter appliance and use "vimtop" | ||
=== Poor performance on vSphere Client or other services === | |||
poor performance can be caused by lack of memory. Check memory used by services with the following command:<syntaxhighlight lang="bash"> | |||
cloudvm-ram-size -J <service name> | |||
cloudvm-ram-size -J vsphere-ui | |||
</syntaxhighlight>Change the heap size for a specific service:<syntaxhighlight lang="bash"> | |||
cloudvm-ram-size -C <ram in MB> <service name> | |||
cloudvm-ram-size -C 700 vsphere-ui | |||
</syntaxhighlight> | |||
Revision as of 12:10, 17 January 2024
Sizing VMs
When choosing number of cpus per socket of VMs you want to pay attention to the processors of the host the vms are running on. You want to maximize the number of vNUMA nodes that are available to the VM. This is based on the architecture of the processors in the host.
By using the least cores per socket you will usually get the best performance.
Be careful as some applications can only use one socket, SQL servers can cause a problem here where you want more cores in the socket.
See here for detailed information https://blogs.vmware.com/vsphere/2013/10/does-corespersocket-affect-performance.html
Performance Monitoring
Monitor the vCenter appliance resources - you can use the VAMI or ssh into the vCenter appliance and use "vimtop"
Poor performance on vSphere Client or other services
poor performance can be caused by lack of memory. Check memory used by services with the following command:
cloudvm-ram-size -J <service name>
cloudvm-ram-size -J vsphere-ui
Change the heap size for a specific service:
cloudvm-ram-size -C <ram in MB> <service name>
cloudvm-ram-size -C 700 vsphere-ui