5.2
Table Of Contents
- VMware Horizon View Architecture Planning
- Contents
- VMware Horizon View Architecture Planning
- Introduction to Horizon View
- Planning a Rich User Experience
- Feature Support Matrix
- Choosing a Display Protocol
- Using View Persona Management to Retain User Data and Settings
- Benefits of Using View Desktops in Local Mode
- Accessing USB Devices Connected to a Local Computer
- Printing from a View Desktop
- Streaming Multimedia to a View Desktop
- Using Single Sign-On for Logging In to a View Desktop
- Using Multiple Monitors with a View Desktop
- Managing Desktop Pools from a Central Location
- Architecture Design Elements and Planning Guidelines
- Virtual Machine Requirements
- Horizon View ESX/ESXi Node
- Desktop Pools for Specific Types of Workers
- Desktop Virtual Machine Configuration
- vCenter Server and View Composer Virtual Machine Configuration
- View Connection Server Maximums and Virtual Machine Configuration
- View Transfer Server Virtual Machine Configuration and Storage
- vSphere Clusters
- Storage and Bandwidth Requirements
- Horizon View Building Blocks
- Horizon View Pods
- Advantages of Using Multiple vCenter Servers in a Pod
- Planning for Security Features
- Understanding Client Connections
- Choosing a User Authentication Method
- Restricting View Desktop Access
- Using Group Policy Settings to Secure View Desktops
- Implementing Best Practices to Secure Client Systems
- Assigning Administrator Roles
- Preparing to Use a Security Server
- Understanding Horizon View Communications Protocols
- Overview of Steps to Setting Up a Horizon View Environment
- Index
RAM Sizing Impact on Storage
The amount of RAM that you allocate to a virtual machine is directly related to the size of the certain files that
the virtual machine uses. To access the files in the following list, use the Windows guest operating system to
locate the Windows page and hibernate files, and use the ESX/ESXi host's file system to locate the ESX/ESXi
swap and suspend files.
Windows page file
By default, this file is sized at 150 percent of guest RAM. This file, which is by
default located at C:\pagefile.sys, causes thin-provisioned storage to grow
because it is accessed frequently. On linked-clone virtual machines, the page
file and temporary files can be redirected to a separate virtual disk that is
deleted when the virtual machines are powered off. Disposable page-file
redirection saves storage, slowing the growth of linked clones and also can
improve performance. Although you can adjust the size from within Windows,
doing so might have a negative effect on application performance.
Windows hibernate file
for laptops
This file can equal 100 percent of guest RAM. You can safely delete this file
because it is not needed in View deployments, even if you use View Client with
Local Mode.
ESX/ESXi swap file
This file, which has a .vswp extension, is created if you reserve less than 100
percent of a virtual machine's RAM. The size of the swap file is equal to the
unreserved portion of guest RAM. For example, if 50 percent of guest RAM is
reserved and guest RAM is 2GB, the ESX/ESXi swap file is 1GB. This file can
be stored on the local datastore on the ESX/ESXi host or cluster.
ESX/ESXi suspend file
This file, which has a .vmss extension, is created if you set the desktop pool
logoff policy so that the virtual desktop is suspended when the end user logs
off. The size of this file is equal to the size of guest RAM.
RAM Sizing for Specific Monitor Configurations When Using PCoIP
If you use PCoIP, the display protocol from VMware, the amount of extra RAM that the ESX/ESXi host requires
depends in part on the number of monitors configured for end users and on the display resolution. Table 4-1
lists the amount of overhead RAM required for various configurations. The amounts of memory listed in the
columns are in addition to the amount of memory required for other PCoIP functionality.
Table 4-1. PCoIP Client Display Overhead
Display
Resolution
Standard Width, in Pixels Height, in Pixels
1-Monitor
Overhead
2-Monitor
Overhead
4-Monitor
Overhead
VGA 640 480 2.34MB 4.69MB 9.38MB
SVGA 800 600 3.66MB 7.32MB 14.65MB
720p 1280 720 7.03MB 14.65MB 28.13MB
UXGA 1600 1200 14.65MB 29.30MB 58.59MB
1080p 1920 1080 15.82MB 31.64MB 63.28MB
WUXGA 1920 1200 17.58MB 35.16MB 70.31MB
QXGA 2048 1536 24.00MB 48.00MB 96.00MB
WQXGA 2560 1600 31.25MB 62.50MB 125.00MB
VMware Horizon View Architecture Planning
36 VMware, Inc.