7.0

Table 16‑1. Example Sizing Table for OS and Persistent Disks
Data Type
Selected Free
Space (GB)
Min Recommended
(GB) 50% Utilization (GB)
Max Recommended
(GB)
OS disks 184.23 40.00 80.00 130.00
Persistent disks 28.56 4.00 10.00 20.00
The Selected Free Space column shows the total available space on all of the datastores that you selected for
a disk type such as OS disks.
The Min Recommended column shows the minimum amount of recommended storage for a pool.
The 50% Utilization column shows the recommended storage when the disks grow to 50% of the parent
virtual machine.
The Max Recommended column shows the recommended storage when the disks approach the full size of
the parent virtual machine.
If you store OS disks and persistent disks on the same datastore, View calculates the storage requirements of
both disk types. The Data Type is shown as Linked clones or Instant clones instead of a particular disk
type.
If you store View Composer replicas on a separate datastore, the table also shows storage recommendations
for the replicas and adjusts the recommendations for OS disks.
Sizing Guidelines for View Composer Linked Clones
The table provides general guidelines. Your storage calculations must account for additional factors that can
affect actual storage growth in the clones.
For OS disks, your sizing estimates depend on how frequently you refresh and recompose the pool.
If you refresh your linked-clone pool between once a day and once a week, make sure that the Selected Free
Space can accommodate storage use between the Min Recommended and 50% Utilization estimates.
If you rarely refresh or recompose the pool, the linked-clone disks continue to grow. Make sure that the
Selected Free Space can accommodate storage use between the 50 % Utilization and Max Recommended
estimates.
For persistent disks, your sizing estimates depend on the amount of Windows profile data that users
generate on their desktops. Refresh and recompose operations do not affect persistent disks.
Sizing Guidelines When You Edit an Existing Desktop Pool
View estimates the storage space that is needed for new clones. When you create a desktop pool, the sizing
guidelines encompass the entire pool. When you edit an existing desktop pool, the guidelines encompass
only the new clones that you add to the pool.
For example, if you add 100 clones to a desktop pool and select a new datastore, View estimates space
requirements for the 100 new clones.
If you select a new datastore but keep the desktop pool the same size, or reduce the number of clones, the
sizing guidelines show as 0. The values of 0 reflect that no new clones must be created on the selected
datastore. Space requirements for the existing clones are already accounted for.
How View Calculates the Minimum Sizing Recommendations
To arrive at a minimum recommendation for OS disks, View estimates that each clone consumes twice its
memory size when it is first created and started up. If no memory is reserved for a clone, an ESXi swap file
is created for a clone as soon as it is powered on. The size of the guest operating system's paging file also
affects the growth of a clone's OS disk.
Setting Up Desktop and Application Pools in View
242 VMware, Inc.