5.2

In this example, the local desktop displayed a message such as "Transferring 871MB".
However, this amount
of data was reduced by deduplication. Although the remaining data could not be compressed, only 2.198MB
of data was transferred over the network.
Guest File System Optimization of Data Transfers
During transfer operations, View Transfer Server reduces the amount of data that must be sent over the network
by taking advantage of guest file system optimization.
When a desktop virtual machine contains a primary NTFS partition, View Transfer Server transfers the blocks
that are allocated by NTFS. Unallocated blocks are not transferred. This strategy minimizes the total number
of blocks to be transferred.
Guest file system optimization occurs only when data is transferred from primary NTFS partitions. View
Transfer Server does not perform this optimization on extended partitions, Logical Disk Manager partitions,
or compressed NTFS volumes on Windows 8, Windows 7, or Windows Vista virtual machines.
Guest file system optimization differs from data deduplication and compression, which also optimize data
transfers but are independent of the desktop's guest operating system. For details about these operations, see
“Optimizing Data Transfers Between Local-Desktop Host Computers and the Datacenter,” on page 323.
Configuring Endpoint Resource Usage
By default, a View desktop that is checked out for use on a local system takes advantage of the memory and
CPU capabilities of that host. The virtual NICs on the desktop use NAT to share the IP and MAC addresses of
the host. You can change this default behavior.
Override Local Usage of Memory and CPU Resources
After a local desktop is checked out, it takes advantage of the memory and CPU capabilities of the local system,
regardless of the memory and CPU settings specified for the virtual machine in vCenter Server. You can
override this default behavior.
By default, the amount of RAM allocated to a View desktop that is checked out for use in local mode is
automatically adjusted to be a certain amount of the RAM that is available on the client host.
The formula takes into consideration how much memory is available to split between the host and guest View
desktop. A Windows XP operating system requires a minimum of 512MB RAM. A 32-bit Windows 8, Windows
7, or Windows Vista operating system requires a minimum of 1GB RAM. The amount of memory available to
split is the total amount of RAM on the host minus the minimum RAM required for the host and guest operating
systems.
Table 14-7. Memory Allotted to Local View Desktops
Memory Allocation Windows XP Guests
Windows 8, Windows 7, and
Vista Guests
Minimum 512MB 1GB
Best effort 512MB + (Available/2) 1GB + (Available/2)
Maximum 2GB 4GB
For example, if a Windows 7 host has a total of 2GB of RAM, to run a Windows 7 View desktop locally would
require 2GB of RAM, with 1GB of RAM allocated to the host and 1GB of RAM allocated to the local View
desktop.
If the host had 3GB of RAM, 1.5GB of RAM would be allocated to the host and 1.5GB of RAM would
be allocated to the local View desktop.
NOTE The automatic adjustment of memory allocation never sets the memory of the local desktop to a lower
value than what is configured in vCenter Server.
VMware Horizon View Administration
328 VMware, Inc.