Architecture Planning

By default, the multiple-monitor configuration matches the host topology. There is extra overhead
precalcuated for more than 2 monitors to accommodate additional topology schemes. If you encounter a
black screen when starting a remote desktop session, verify that the values for the number of monitors and
the display resolution, which are set in View Administrator, match the host system, or manually adjust the
amount of memory by using selecting Manage using vSphere Client in View Administrator and then set
the total video memory value to maximum of 128MB.
RAM Sizing for Specific Workloads and Operating Systems
Because the amount of RAM required can vary widely, depending on the type of worker, many companies
conduct a pilot phase to determine the correct setting for various pools of workers in their enterprise.
A good starting point is to allocate 1GB for 32-bit Windows 7 or later desktops and 2GB for 64-bit
Windows 7 or later desktops. If you want to use one of the hardware accelerated graphics features for 3D
workloads, VMware recommends 2 virtual CPUs and 4GB of RAM. During a pilot, monitor the performance
and disk space used with various types of workers and make adjustments until you find the optimal setting
for each pool of workers.
Estimating CPU Requirements for Virtual Machine Desktops
When estimating CPU, you must gather information about the average CPU utilization for various types of
workers in your enterprise.
CPU requirements vary by worker type. During your pilot phase, use a performance monitoring tool, such
as Perfmon in the virtual machine, esxtop in 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:
n
Software developers or other power uses with high-performance needs might have much higher CPU
requirements than knowledge workers and task workers. Dual or Quad virtual CPUs are recommended
for 64-bit Windows 7 virtual machines running compute-intensive tasks such as using CAD
applications, playing HD videos, or driving 4K display resolutions.
n
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:
n
Use View Composer to update images rather than having software management agents download
software updates to each individual virtual desktop.
n
Schedule antivirus and software updates to run at nonpeak hours, when few users are likely to be
logged in.
n
Stagger or randomize when updates occur.
n
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 and later.
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 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.
Chapter 4 Architecture Design Elements and Planning Guidelines for Remote Desktop Deployments
VMware, Inc. 47