5.2

Best Practices for Deploying Local Desktops
Best-practice recommendations address questions about the memory, processing power, and number of the
various components that affect a local mode deployment.
General Recommendations for Most Deployments
Virtual machine
configuration
Desktops that run in local mode automatically adjust the amount of memory
and processing power they use based on that available from the client
computer.
Because of this capability, you can configure the minimum amount
of RAM and virtual CPUs required by the guest operating system when you
create the virtual machine in vCenter Server.
View Transfer Server
Some features of View Transfer Server are CPU-intensive. If you plan to use
SSL for local mode operations such as checking out and checking in desktops
or for replicating data back to the datacenter, the virtual machine hosting the
Transfer Server might need an additional virtual CPU. You might also need
more processing power if you turn on compression for replication operations.
For minimum memory and processor requirements, see the topic in the View
Installation document about system requirements for View Transfer Server.
When determining how many View Transfer Server instances to add to View
Connection Server, determine whether high availability is an important
consideration. If it is, add at least two instances. If one Transfer Server goes
down, View Connection Server automatically sends requests to the other one.
When calculating how many Transfer Server instances you need, also take into
consideration how many end users are likely to be replicating data or checking
out or checking in desktops at the same time. Each Transfer Server instance can
accommodate 60 concurrent disk operations, though network bandwidth will
likely be saturated at a lower number. VMware tested 20 concurrent disk
operations, such as 20 clients downloading a local desktop at the same time,
over a 1GB per second network connection.
Transfer Server
Repository
Base images of View Composer linked-clone desktops are kept in the Transfer
Server Repository, on a network share. The faster your network storage disks
are, the better performance will be.
Pool settings
Use View Composer to create pools of linked-clone desktops. When using the
Create Pool wizard, choose dedicated assignment and create the pool only for
desktops that are intended to be used in local mode. Local mode virtual
machines can be placed on datastores with lower IOPS than storage intended
to support large numbers of remote View desktops.
Data replication
Determine whether end users will need to replicate OS disk data, such as that
contained in a customization specification. If not, set a policy so that only
persistent disks are replicated.
If you set an automatic replication interval, use the default of every 12 hours
or set an interval that is even less frequent.
Do not turn on deduplication or compression unless you notice problems due
to a slow network connection. The deduplication and compression features
reduce the amount of network bandwidth required at the expense of increased
processing power required on the end user's computer or on the Transfer
Server.
VMware Horizon View Administration
308 VMware, Inc.