When estimating CPU, you must gather information about the average CPU utilization for various types of workers in your enterprise.

Note

This topic addresses issues regarding CPU requirements when accessing View desktops remotely. If users run a View desktop in local mode on their client systems, the View desktop uses the available CPUs on the client device, up to 2 CPUs.

CPU requirements vary by worker type. During your pilot phase, use a performance monitoring tool, such as Perfmon in the virtual machine, esxtop in ESX/ESXi, or vCenter Server performance monitoring tools, to understand both the average and peak CPU use levels for these groups of workers. Also use the following guidelines:

Software developers or other power uses with high-performance needs might have much higher CPU requirements than knowledge workers and task workers. Dual virtual CPUs are recommended for compute-intensive tasks, if you need to play 720p video using the PCoIP display protocol, and for Windows 7 and later desktops.

Single virtual CPUs are generally recommended for other cases.

Because many virtual machines run on one server, CPU can spike if agents such as antivirus agents all check for updates at exactly the same time. Determine which agents and how many agents could cause performance issues and adopt a strategy for addressing these issues. For example, the following strategies might be helpful in your enterprise:

Use View Composer to update images rather than having software management agents download software updates to each individual virtual desktop.

Schedule antivirus and software updates to run at nonpeak hours, when few users are likely to be logged in.

Stagger or randomize when updates occur.

Use an antivirus product that is compatible with the VMware vShield API. For example, this API has been integrated into VMware vCloud® Networking and Security 5.1.

As an informal initial sizing approach, to start, assume that each virtual machine requires 1/8 to 1/10 of a CPU core as the minimum guaranteed compute power. That is, plan a pilot that uses 8 to 10 virtual machines per core. For example, if you assume 8 virtual machines per core and have a 2-socket 8-core ESX/ESXi host, you can host 128 virtual machines on the server during the pilot. Monitor the overall CPU usage on the host during this period and ensure that it rarely exceeds a safety margin such as 80 percent to give enough headroom for spikes.