VMware VIEW COMPOSER 2.5 - ARCHITECTURE PLANNING EN-000350-01 Specifications download pdf (Page 34)

The amount of storage space required must take into account the following files for each virtual desktop:

The ESX suspend file is equivalent to the amount of RAM allocated to the virtual machine.

The Windows page file is equivalent to 150 percent of RAM.

Log files take up approximately 100MB for each virtual machine.

The virtual disk, or .vmdk file, must accommodate the operating system, applications, and future

applications and software updates. The virtual disk must also accommodate local user data and user-

installed applications if they are located on the virtual desktop rather than on file shares.

If you use View Composer, the .vmdk files grow over time, but you can control the amount of growth by

scheduling View Composer refresh operations, setting a storage over-commit policy for View desktop

pools, and redirecting Windows page and temporary files to a separate, nonpersistent disk.

You can also add 15 percent to this estimate to be sure that users do not run out of disk space.

VMware View ESX Node

A node is a single VMware ESX server that hosts virtual machine desktops in a VMware View deployment.

VMware View is most cost-effective when you maximize the consolidation ratio, which is the number of

desktops hosted on an ESX server. Although many factors affect server selection, if you are optimizing strictly

for acquisition price, you must find server configurations that have an appropriate balance of processing power

and memory.

There is no substitute for measuring performance under actual, real world scenarios, such as in a pilot, to

determine an appropriate consolidation ratio for your environment and hardware configuration.

Consolidation ratios can vary significantly, based on usage patterns and environmental factors. Use the

following guidelines:

As a general framework, consider compute capacity in terms of 8 to 10 virtual desktops per CPU core. For

information about calculating CPU requirements for each virtual machine, see “Estimating CPU

Requirements for Virtual Desktops,” on page 33.

Think of memory capacity in terms of virtual desktop RAM, host RAM, and overcommit ratio. Although

you can have between 8 and 10 virtual desktops per CPU core, if virtual desktops have 1GB or more of

RAM, you must also carefully consider physical RAM requirements. For information about calculating

the amount of RAM required per virtual machine, see “Estimating Memory Requirements for Virtual

Desktops,” on page 31.

Note that physical RAM costs are not linear and that in some situations, it can be cost-effective to purchase

more smaller servers that do not use expensive DIMM chips. In other cases, rack density, storage

connectivity, manageability and other considerations can make minimizing the number of servers in a

deployment a better choice.

Finally, consider cluster requirements and any failover requirements. For more information, see

“Determining Requirements for High Availability,” on page 42.

For information about specifications of ESX hosts in vSphere, see the VMware vSphere Configuration Maximums

document.

VMware View Architecture Planning Guide

34 VMware, Inc.

1 2 ... 29 30 31 32 33 34 35 36 37 38 39 ... 71 72

No comments

VMware VIEW COMPOSER 2.5 - ARCHITECTURE PLANNING EN-000350-01 Specifications Page 34