Top Features Controlled by VMware vCenter for Optimal Performance
This blog post lists VMware vCenter recommended configurations and best practices for optimal performance. This also includes some features which are controlled or accessed via vCenter.
✓ Whether run on virtual machines or physical systems, ensure you provide vCenter Server and the vCenter Server database along with sufficient memory, CPU, and storage resources (both capacity and performance) for your deployment size.
✓ Because of the significance of the database to vCenter performance, ensure to follow the recommendations as per the “VMware vCenter Database Considerations”.
✓ The performance of vCenter Server depends mostly on the number of managed attributes and entities (hosts and virtual machines) and the total number of connected VMware vSphere Clients.
Exceeding the maximums mentioned in Configuration Maximums for vSphere 6.0, moreover, in addition to being unsupported, it is likely to affect and impact vCenter Server performance.
✓ To reduce the latency of vCenter operations, maintain the minimum number of network hops among the vCenter Server system and also at the vCenter Server database.
✓ Be cautious about the network latency between vCenter Server and the hosts it manages, as it might impact the performance of operations consisting of those hosts.
✓ The vCenter Inventory Service and the vSphere Web Client Server might be executed on the same system as vCenter Server, however, for maximum performance on heavily-loaded vCenter systems, consider executing the vSphere Web Client Server on a separate system.
✓ The VMware vSphere Update Manager might be executed on the same system and utilize the same database as vCenter Server, however, for maximum performance on heavily-loaded vCenter systems, acknowledge running Update Manager on its own system and offering it with a dedicated database.
✓ While installation of VMware vCenter you might be asked to select a target inventory size. This option will be utilized to set Java virtual machine (JVM) maximum heap memory sizes for various other services.
The default acknowledged values (detailed in the 6.0 version of vSphere Installation and Setup, search for “Tomcat Server settings”) must provide good performance while restraining unessential memory commitment.
In case you will have inventory sizes well into the very large range (as declared in the 6.0 version of vSphere Setup and Installation, search for “vCenter Server for Windows Hardware Requisitions“), but, you might get better performance by maximizing one or more of these settings.