05-25-202211:08 AM - last edited on 09-21-202204:14 AM by Anusha_Vemula
vSZ requires enough hardware resources to sustain the service. vSZ cannot support deployment in low performance hypervisor.
During the time of deployment or upgrade it is always a good practice to reconfirm and validate the resource requirements of vSZ and validate the system performance:
Use the SZ CLI in debug-tools > system > system performance. The command will run system benchmark on CPU and IO for vSZ.
Note: Disks IO is most important in vSZ cluster. Disk IO is the slowest subsystem in a server, which means that write-heavy clusters can easily saturate their disks, which in turn become the bottleneck of the cluster.
The vSZ resource requirements for the deployment will vary from the VM deployment type - Essentials or High Scale and the Virtual Platform – Cloud or on-premises
In case of a cluster with multiple nodes, every node is expected to have the same SKU or resource allocation, and it is not recommended to run multiple vSZs on the same VM hardware for high end deployment.
Any resource modification would need to power off the SZ instance prior to the change and then power on the same to take effect
The required resources for a type of deployment can be verified from: