VMware View on Nutanix Best Practices v2.0 – December 2012

Copyright 2012 Nutanix, Inc.

Nutanix, Inc. 1735 Technology Drive, Suite 575 San Jose, CA 95110

All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws.

Nutanix is a trademark of Nutanix, Inc. in the United States and/or other jurisdictions. All other marks and names mentioned herein may be trademarks of their respective companies.

3

View on Nutanix | 3

Table of Contents

1 Executive Summary ..................................................................................... 5

2 Introduction .................................................................................................. 6

2.1 Audience ................................................................................................... 6

2.2 Purpose ..................................................................................................... 6

3 Best Practice Checklist ............................................................................... 7

4 Best Practice Detail ..................................................................................... 9

4.1 Desktops ................................................................................................... 9

4.1.1 Sizing ........................................................................................................... 9

4.1.2 VM Configuration....................................................................................... 10

4.1.3 OS Optimization ........................................................................................ 10

4.1.4 Application Delivery ................................................................................... 10

4.1.5 Profile Management & User Data ............................................................. 11

4.2 VMware View .......................................................................................... 12

4.2.1 Architecture ............................................................................................... 12

4.2.2 Host Caching ............................................................................................. 12

4.2.3 Desktop Pools ........................................................................................... 13

4.3 VMware vSphere ..................................................................................... 17

4.3.1 VM Memory ............................................................................................... 17

4.3.2 Host Power Policy ..................................................................................... 17

4.3.3 Host Cache / VM Swap ............................................................................. 17

4.3.4 Content-Based Read Cache ..................................................................... 17

4.3.5 Datastores ................................................................................................. 18

4.3.6 Resource Pools ......................................................................................... 18

4.4 Nutanix .................................................................................................... 20

4.4.1 Controller VM Resources .......................................................................... 20

H

4

View on Nutanix | 4

4.4.2 Nutanix gflags ............................................................................................ 20

4.5 Active Directory ....................................................................................... 20

4.5.1 Domain / DNS ........................................................................................... 20

4.5.2 Desktop Group Policy ............................................................................... 20

4.6 Network ................................................................................................... 21

4.6.1 LAN ........................................................................................................... 22

4.6.2 WAN .......................................................................................................... 22

5 Conclusion ................................................................................................. 23

6 References ................................................................................................. 24

H

5

View on Nutanix | 5

1 Executive Summary

Nutanix Complete Cluster is a scalable virtualization platform for desktop, server, and big-data deployments. This document makes recommendations for the optimization and scaling of VMware View deployments on Nutanix. It shows the scalability of the Nutanix Complete Cluster and provides detailed performance and configuration information on the scale-out capabilities of the cluster. The Nutanix Complete Cluster consists of modular “blocks” that include compute, storage, and network. This design greatly reduces cost while increasing performance and scalability empowering you to deliver a reliable and consistent user-experience. The Nutanix Distributed File System (NDFS), the core of Nutanix Complete Cluster, tethers high-performance solid-state storage directly to enterprise applications while preserving the high capacity that the SATA HDD tier provides through its adaptive information lifecycle management (ILM) capabilities. NDFS amplifies the power of server-attached flash in the realm of enterprise virtualization by colocating high-performance, localized storage I/O with Google-like, scale-out distributed redundancy via high speed 10 GbE top-of-rack switches. The base cluster ships with four industry-standard x86 servers bundled with VMware's hypervisor in a 2U, 85-lb., SAN-free server appliance. The solution and testing provided in this document was completed with VMware View 5.1 deployed on VMware vSphere on the Nutanix Complete Cluster.

Simplified. Software Defined. Nutanix.

H

6

View on Nutanix | 6

2 Introduction

2.1 Audience

This best practices document is part of the Nutanix Solutions Library and is intended for use by individuals responsible for the architecture, design, management, and support of Nutanix infrastructures. Consumers of this document should be familiar with concepts pertaining to VMware View, VMware vSphere, and Nutanix.

We have broken down this document to address to key items for each role focusing on the enablement of a successful design, implementation, and transition to operation.

2.2 Purpose

This document covers the following subject areas:

o Overview of high-level VMware View best practices for Nutanix

o Expanded detail on VMware View best practices for Nutanix

If you are interested in the high-level best practices continue with the “Best Practice Checklist” section below.

If you want to jump into the detailed items, see “Best Practice Detail” on page 9.

H

7

View on Nutanix | 7

3 Best Practice Checklist

The VMware View on Nutanix best practices can be summarized into the following items:

General o Perform a current state analysis to identify workloads and sizing for desktops to be

migrated to virtual desktops.

o Spend time up front to architect a solution that meets both current and future needs.

o Design for end-user experience to deliver consistent performance, reliability, and scale.

o Start with a PoC, test, optimize, iterate, scale.

Core Components o Desktops

▫ Size desktops appropriately for your particular use case.

▫ Use a mix of applications installed in gold images and application virtualization, depending on the scenario.

▫ Disable unnecessary OS services and applications.

▫ Redirect home directories or use a profile management tool for user profiles and documents.

▫ Set mks.poll.headlessRates in base VM.

o VMware View

▫ Design for reliability and scale.

▫ Utilize Host Caching (View 5.1+ only).

▫ Disable Host Caching digest re-computation during work hours.

▫ Redirect home directory or use a profile management tool (i.e. View Persona Management) for user profiles and documents.

▫ Redirect disposable disks.

▫ Use PCoIP and optimize PCoIP settings.

o VMware vSphere

▫ Follow VMware best practices.

▫ Keep number of VMs per ESXi host to the following:

VMs to ESXi host physical core ratio ~ 8:1

vCPU to ESXi host physical core ratio ~ 16:1

vRam to ESXi host physical ram ratio ~ 1.1:1

▫ Enable ‘High Performance’ host power policy.

▫ Enable ‘Host Cache’.

▫ Enable CBRC and digests on base VMs and templates (non-View 5.1).

H

8

View on Nutanix | 8

▫ Lock desktop VM memory.

▫ Use resource pools.

o Nutanix

▫ Use a single container and datastore.

▫ Optimize gflags based upon applications and use case.

▫ Increase Nutanix Controller VM memory to 12 GB.

Supporting Components o Active Directory

▫ Have local GCs and DNS servers at each site.

▫ Redirect home profiles for users.

▫ Create PCoIP policy for desktop optimizations.

▫ Configure DNS scavenging.

o DHCP

▫ Reduce default DHCP lease times for VDI scope from 8 days to 1 hour.

o File Services

▫ Utilize DFS for user data and replication from site to DC.

▫ Map home directory redirection to DFS namespace.

▫ Implement domain-based file services with Windows Server 2008 Mode.

o Virus Scan

▫ Schedule scans to run outside business hours.

▫ Stagger system scans in phases.

o Network

▫ Utilize and optimize QoS for View PCoIP traffic.

▫ Use 1 Gb or greater access ports for end-user LAN connectivity.

▫ Ensure adequate bandwidth for WAN and VPN clients.

o OS and Application Updates

▫ Schedule updates to be applied outside business hours to avoid performance impacts.

▫ Stagger updates in phases.

H

9

View on Nutanix | 9

4 Best Practice Detail

This section covers the detailed best practices and concepts for deploying VMware View on Nutanix.

4.1 Desktops

4.1.1 Sizing

The following are typical scenarios for desktop deployment and utilization.

Table 1: Desktop Scenario Definition

Scenario Definition Kiosk Users These users need to share a desktop that is located in a public place.

Examples of kiosk users include students using a shared computer in a classroom, nurses at nursing stations, and computers used for job placement and recruiting. These desktops require automatic login. Authentication can be done through certain applications if necessary.

Task Workers Task workers and administrative workers perform repetitive tasks within a small set of applications, usually at a stationary computer. The applications are usually not as CPU- and memory-intensive as the applications used by knowledge workers. Task workers who work specific shifts might all log in to their virtual desktops at the same time. Task workers include call center analysts, retail employees, and warehouse workers.

Knowledge Workers Knowledge workers’ daily tasks include accessing the Internet, using email, and creating complex documents, presentations, and spreadsheets. Knowledge workers include accountants, sales managers, and marketing research analysts.

Power Users Power users include application developers and people who use graphics-intensive applications.

Below are some initial recommendations for desktop sizing for a Windows 7 desktop:

Table 2: Desktop Scenario Sizing

Scenario vCPU Memory Disks Kiosk Users 1 1 25GB (OS) Task Workers 1-2 1 40GB (OS) Knowledge Workers 1-2 2 40GB (OS) Power Users 2+ 2+ 40GB (OS)

Note: These are recommendations for sizing and should be modified after a current state analysis.

H

1

View on Nutanix | 10

4.1.2 VM Configuration

Use the following settings when configuring your base VM:

Table 3: Desktop VM Configuration

Parameter Configuration Network adapter Vmxnet3 Storage adapter PVSCSI (preferred) or LSI Logic SAS VMware tools Latest installed Memory Locked (preferred) VM Logging Disabled View Agent Latest installed Advanced VM configuration parameters

Name: mks.poll.headlessRates Value: 1000 100 2

4.1.3 OS Optimization

Configure your Windows 7 image to the specifications outlined in the VMware View Optimization Guide for Windows 7. Here is a summary of the optimizations:

o Set display to “Adjust for best performance”

o Disable Windows indexing service

o Anti-Virus

▫ Full Clones: Run ESXi level anti-virus scans and if necessary; run OS level anti-Virus full scan jobs during off-hours and in phases

▫ Linked Clones: Run ESXi level anti-virus scan jobs during off-hours and in phases

o Updates

▫ Full Clones: Update OS during off-hours and in phases

▫ Linked Clones: Update base image during off-hours and recompose in phases

Nutanix recommends using either the CommandsNoPersonaManagement or CommandsPersonaManagement script to prepare Win 7 golden image. These scripts are included as part of the VMware View Optimization Guide for Windows 7 and are attached to this document.

4.1.4 Application Delivery

For common applications which will be used by a majority of users, it normally makes sense to install the applications onto the base image. However, in some cases utilization of application virtualization can be beneficial or may be used temporarily until added into the golden image and the environment is recomposed or refreshed.

Common application virtualization options are:

o VMware ThinApp

H

1

View on Nutanix | 11

o Citrix XenApp

o Windows Remote Desktops Services (RemoteApp)

o Microsoft App-V

o Unidesk

4.1.5 Profile Management & User Data

Using a profile management platform can have extensive benefits when managing VDI environments and maintaining user experience.

Active Directory user profile best practices recommend redirecting user profiles and host directories to a fileserver in most cases. User profile redirection is configured as part of Active Directory settings and provides the following benefits:

o Centralized management of user profiles and data

o Simplified backups

o Removing data layer from VDI-linked clone

Common profile management options are:

o VMware View Persona Management

o Liquidware Labs

o Unidesk

o AppSense

The following diagram shows the decoupling of the user persona from the desktop.

Figure 1. Persona Decoupling

H

1

View on Nutanix | 12

4.2 VMware View

4.2.1 Architecture

Nutanix allows you to start small and scale from hundreds to thousands of desktops. To enable this scale and growth it is critical to design a solution with scalability in mind.

Below is example architecture using a Pod methodology for designing either a small or massive scale VMware View infrastructure with Nutanix:

Figure 2. VMware View Pod Architecture

For more information on VMware View on Nutanix design refer to the VMware View on Nutanix Reference Architecture on http://www.nutanix.com/resources.html#Collateral.

4.2.2 Host Caching

Host caching creates an in-memory cache on each ESXi host which will be utilized to cache frequently accessed blocks locally, which improves performance and decreases the amount of I/O going over the network. In conjunction with localized I/O in a Nutanix cluster, host caching provides the highest possible desktop performance.

H

1

View on Nutanix | 13

4.2.3 Desktop Pools

This section contains recommended pool configurations for various desktop scenarios.

4.2.3.1 Kiosk User Scenario Table 4: Kiosk User - Pool Configuration

Item Detail Pool Type Automated User Assignment Floating Clone Type View Composer Linked Clones View Composer Disks o Persistent Disk: Don’t redirect (Use home directory redirection or

Profile management system)

o Disposable File Redirection: Redirect Datastore(s) One NFS Datastore for all VMs (linked clone, replica, VAAI, etc.) Advanced Storage Options o Non-VCAI: Do not check Use native NFS snapshots (VAAI)

Host Caching Enabled, digest re-computation scheduled for off-work hours (M-F / 9-5)

Table 5: Kiosk User - Pool Settings

Parameter Configuration General State Default Connection server restrictions Default Remote Settings Remote desktop power policy Default Automatically logoff after disconnect Immediately Allow users to reset their desktops No Refresh OS disk after logoff Always or determined by need Remote Display Protocol Default display protocol PCoIP Allow users to choose protocol No Windows 7 3D rendering N/A Max number of monitors 1 Max resolution of any one monitor 1680×1050 Adobe Flash Settings for Remote Sessions Adobe Flash quality Default or determined by need Adobe Flash throttling Default or determined by need

H

1

View on Nutanix | 14

4.2.3.2 Task Worker Scenario Table 6: Task Worker - Pool Configuration

Item Detail Pool Type Automated User Assignment Floating or Dedicated Clone Type View Composer Linked Clones View Composer Disks o Persistent Disk: Don’t redirect (Use home directory redirection or

profile management system)

o Disposable File Redirection: Redirect Datastore(s) 1 × NFS Datastore for all VMs (linked clone, replica, VAAI, etc.) Advanced Storage Options o Non-VCAI: Do not check Use native NFS snapshots (VAAI)

o VCAI: Check Use native NFS snapshots (VAAI) Host Caching Enabled, digest re-computation scheduled for off-work hours (M-F / 9-5)

Table 7: Task Worker - Pool Settings

Parameter Configuration General State Default Connection server restrictions Default Remote Settings Remote desktop power policy Default Automatically logoff after disconnect Immediately Allow users to reset their desktops Default Refresh OS disk after logoff Never or determined by need Remote Display Protocol Default display protocol PCoIP Allow users to choose protocol No Windows 7 3D rendering N/A Max number of monitors 1 Max resolution of any one monitor 1680×1050 Adobe Flash Settings for Remote Sessions Adobe Flash quality Default or determined by need Adobe Flash throttling Default or determined by need

H

1

View on Nutanix | 15

4.2.3.3 Knowledge Worker Scenario Table 8: Knowledge Worker - Pool Configuration

Item Detail Pool Type Automated User Assignment Dedicated (enable automatic assignment) Clone Type View Composer Linked Clones View Composer Disks o Persistent Disk: Don’t redirect (Use home directory redirection or

profile management system)

o Disposable File Redirection: Redirect Datastore(s) 1 × NFS Datastore for all VMs (linked clone, replica, VAAI, etc.) Advanced Storage Options o Non-VCAI: Do not check Use native NFS snapshots (VAAI)

o VCAI: Check Use native NFS snapshots (VAAI) Host Caching Enabled, digest re-computation scheduled for off-work hours (M-F / 9-5)

Table 9: Knowledge Worker - Pool Settings

Parameter Configuration General State Default Connection server restrictions Default Remote Settings Remote desktop power policy Default Automatically logoff after disconnect Never Allow users to reset their desktops Default Refresh OS disk after logoff Never or determined by need Remote Display Protocol Default display protocol PCoIP Allow users to choose protocol No Windows 7 3D rendering Determined by need Max number of monitors 2 Max resolution of any one monitor 1680×1050 Adobe Flash Settings for Remote Sessions Adobe Flash quality Default or determined by need Adobe Flash throttling Default or determined by need

H

1

View on Nutanix | 16

4.2.3.4 Power User Scenario Table 10: Power User - Pool Configuration

Item Detail Pool Type Automated / Manual (If importing existing) User Assignment Dedicated (enable automatic assignment) Clone Type Full or VCAI Clones View Composer Disks o Persistent Disk: Don’t redirect (Use home directory redirection or

profile management system)

o Disposable File Redirection: Redirect Datastore(s) 1 × NFS Datastore for all VMs (linked clone, replica, VAAI, etc.) Advanced Storage Options o If VCAI: Check Use native NFS snapshots (VAAI)

Host Caching Enabled, digest re-computation scheduled for off-work hours (M-F / 9-5)

Table 11: Power User - Pool Settings

Parameter Configuration General State Default Connection server restrictions Default Remote Settings Remote desktop power policy Default Automatically logoff after disconnect Never Allow users to reset their desktops Default Refresh OS disk after logoff Never Remote Display Protocol Default display protocol PCoIP Allow users to choose protocol No Windows 7 3D rendering Yes → 128MB Max number of monitors 2 Max resolution of any one monitor Default Adobe Flash Settings for Remote Sessions Adobe Flash quality Default Adobe Flash throttling Default

H

1

View on Nutanix | 17

4.3 VMware vSphere

4.3.1 VM Memory

VM version 8 has an option to reserve all VM memory. This setting ensures that host memory is not overcommitted and removes the need for .vswp files, freeing up storage space.

It is normally recommended to lock VM memory and then, if necessary, to gradually overcommit host memory after steady-state analysis.

4.3.2 Host Power Policy

The new Intel® chipsets include Speed Step Technology™, which dynamically adjusts CPU performance based on load. To get the best possible performance, set the power policy to High Performance, which disables CPU power management features.

4.3.3 Host Cache / VM Swap

Host cache allows a Nutanix cluster to leverage a local SSD for VM level swap. VMware vSphere environments have two types of swap:

o Operating System Swap OS swap is used when the OS is out of physical memory (Pagefile.sys in Windows or /SWAP in Linux). OS swap has the disadvantage of incurring a great deal of overhead.

o Virtual Machine Swap VM swap ensures that the VM has memory even if they physical host memory is fully utilized. A .vswp file is created for memory when is not explicitly reserved / locked and backed by actual host memory. The size of the .vswp file is determined by the vRam assigned to the VM: VM Memory – Memory Reservation Size = .vswp size

Host cache dedicates space on the ESXi host local SSDs, which VMkernel will utilize for VM swap (.vswp). Host cache creates a number of 1 GB .vswp files on the local SSD which VMkernel will dynamically use for VM swap. In the case where the host cache is full, the traditional .vswp files with the VM will be leveraged.

Using host cache provides the following benefits:

o Higher performance for VM swap

o Faster vMotion and HA events as secondary VM swap is stored on shared storage and doesn’t need to be re-created on the target host in the case of a vMotion or HA event

o Efficient oversubscribing of ESXi host physical memory

4.3.4 Content-Based Read Cache

Content-based read cache (CBRC) is an ESXi side cache which can be used for caching VMDK data in ESXi memory. CBRC allows a request for a VMDK or disk to be served from memory, which reduces the number of IOPS over the network. The main use case for CBRC is dealing with VDI where a large number of read requests are “forwarded” to the replica disk which is

H

1

View on Nutanix | 18

hosted on a single datastore. With CBRC a great deal of these read requests can be served from memory with a significant performance benefit.

Note: With View 5.1 this can be automatically configured as part of the View/Pool configuration. For View 5.0 or general use this will need to be configured manually.

4.3.5 Datastores

Because of the localized I/O that Nutanix provides, we can very easily configure our storage for VDI and linked clones. It is recommended to create a single NFS container which is mounted as a datastore, simplifying the View configuration and providing a single datastore for all linked clones.

Figure 3. Linked Clone Structure

4.3.6 Resource Pools

Using resource pools, which is a vSphere best practice, offers an easy way to control resource management. Requirements for resource pools should be derived from the needs of the environment.

Here are considerations for designing a resource pool structure:

o Reservations and shares

▫ What % of resources do I want to reserve for a particular set of VMs?

▫ What % of shares do I want to entitle for a group of VMs?

o Two top-level resource pools at a minimum

H

1

View on Nutanix | 19

▫ Infrastructure: Nutanix Controller VMs, essential infrastructure VMs

▫ Tenant: User VMs

o VMs and Resource Pools should not be on the same level This can lead to situations where a VM can have the same right to resources as a resource pool containing multiple VMs and is normally a misconfiguration

Following is an example resource pool structure. Note: Given the desktop sizing and quantity per tier the shares values per tier might need to be re-balanced.

Tenan

t

70%

Platin

um

40%

Gold

30%

Silver

20%

Datac

ente

r

VMware

vCen

ter

Norm

al

30%

Bronze

10%

Infra

stru

cture

30%

Nutanix

SVMs

VMwareESXi

1

VMwareESXi16

Clust

er

Non-E

ssen

tial

Servic

es

Esse

ntial

Servic

es

Critica

l

70%

...

Figure 4. Resource Pool Structure Example

H

2

View on Nutanix | 20

4.4 Nutanix

4.4.1 Controller VM Resources

The following values have been configured and validated to give the best possible performance for View or other VDI deployments.

Note: The cluster must be down and controller VMs powered off to make the modifications to the controller VMs memory and resource settings.

Table 12: Nutanix CVM Resources

Parameter Configuration Memory Size Increase to 12 GB Memory Reservation Increase to 12 GB

4.4.2 Nutanix gflags

The Nutanix platform implements configurable parameters as gflags. Please contact your Nutanix Systems Engineer or Support Engineer to obtain the latest gflag tuning parameters for your Nutanix Release. Gflag changes should only be performed under the direct supervision of Nutanix Support or a Nutanix certified Systems Engineer.

4.5 Active Directory

4.5.1 Domain / DNS

Always have a local GC / DNS server at the site and preferably hosted on Nutanix. This will increase logon speeds due to local network I/O for GPO application and access to Sysvol.

4.5.2 Desktop Group Policy

The optimal registry configuration can be summarized by the following computer configuration policy items:

Table 13: Desktop Registry Policy Keys

Key Value Name Data Type Value HKLM\System\CurrentControlSet\Services\Afd\Parameters

FastSendDatagramThreshold REG_DWORD 1500

Table 14: Desktop PCoIP Policy Parameters

Parameter Configuration Turn off Build-to-Lossless feature Enabled Configure the PCoIP session audio bandwidth limit High bandwidth: 1500Kbps

Medium bandwidth: 400Kbps

H

2

View on Nutanix | 21

Low bandwidth: 90Kbps Maximum initial image quality High bandwidth: 90 (default)

Medium bandwidth: 70 Low bandwidth: 70

Minimum image quality High bandwidth: 50 (default) Medium bandwidth: 50 Low bandwidth: 50

Maximum frame rate High bandwidth: 30+ Medium bandwidth: 20-30 (default) Low bandwidth: 10

Configure the maximum PCoIP session bandwidth LAN: N/A WAN: Peak desktop bandwidth (see network section below)

Configure the PCoIP session bandwidth floor

0-100,000Kbps (sum of all floors must be less than network capability)

The optimal PCoIP configuration can be summarized by the following items above. For more information, refer to the VMware View PCoIP Optimization Guide.

4.6 Network

When planning for estimated network bandwidth requirements, use the following estimated values:

o 100 to 150 Kbps average bandwidth for a basic office productivity desktop: typical office applications with no video, no 3D graphics, and the default Windows and VMware View settings.

o 50 to 100 Kbps average bandwidth for an optimized office productivity desktop: typical office applications with no video, no 3D graphics, with Windows desktop settings optimized and VMware View optimized.

o 400 to 600 Kbps average bandwidth for virtual desktops utilizing multiple monitors, 3D, Aero, and Office 2010.

o 500 Kbps to 1 Mbps minimum peak bandwidth to provide headroom for bursts of display changes. In general, size your network using the average bandwidth, but consider peak bandwidth to accommodate bursts of imaging traffic associated with large screen changes.

o 2 Mbps per simultaneous user running 480p video, depending upon the configured frame rate limit and the video type.

o 80% of the bandwidth will be used consistently.

Consider the percentage of users who will use 3D graphics. You might balance users who will use 3D with other users who will not use 3D graphics. Those using 3D will have higher bandwidth utilization. With the reduced bandwidth consumption in View 5, adding 3D users is satisfactory on a WAN with up to approximately 100 ms latency.

H

2

View on Nutanix | 22

4.6.1 LAN

Taking the general network assumptions into account, configure the LAN as follows:

o Utilize 1 Gb access ports for end-user device connectivity.

o Ensure MTU is a minimum of 1500 throughout the network.

o Ensure full-duplex throughout the network.

o Utilize QoS/CoS if available (specify as real-time and above TCP but below VoIP).

o Place desktops on a dedicated network / VLAN and optimize for latency and throughput.

4.6.2 WAN

Taking the general network assumptions into account, configure the WAN as follows:

o Do not route PCoIP traffic through TCP-based SSL tunnels.

o Ensure UDP traffic is available over VPN.

o Ensure MTU is a minimum of 1500 throughout the network.

o Place desktops on a dedicated network / VLAN and optimize for latency and throughput.

o Utilize QoS/CoS if available (specify as real-time and above TCP but below VoIP).

o Ensure round-trip network latency is less than 250 ms.

o Size WAN bandwidth between sites using the desktop throughput assumptions above.

▫ Example calculation: WAN bandwidth required = (# of users × average bandwidth) / 0.8

▫ Example calculation: # of users supported by WAN = (WAN bandwidth × 0.8) / average bandwidth

o In branch office deployments, primary desktops should be local with secondary in the datacenter.

H

2

View on Nutanix | 23

5 Conclusion

The Nutanix VMware View solution provides the best of many worlds: industry leading performance with the ability to run multiple mixed workloads on a single converged architecture. Of the “converged” architectures in the market today, none can truly provide the optimal configuration for all workloads; however this is has changed with Nutanix.

As part of its continuous determination to deliver the best possible solutions, Nutanix will continue to research into the following areas:

o Benchmarks

o Performance Optimizations

o Scale Testing

H

2

View on Nutanix | 24

6 References

Table of Figures

Figure 1. Persona Decoupling .................................................................................................... 11

Figure 2. VMware View Pod Architecture ................................................................................... 12

Figure 3. Linked Clone Structure ................................................................................................ 18

Figure 4. Resource Pool Structure Example ............................................................................... 19

Table of Tables

Table 1: Desktop Scenario Definition ............................................................................................ 9

Table 2: Desktop Scenario Sizing ................................................................................................. 9

Table 3: Desktop VM Configuration ............................................................................................ 10

Table 4: Kiosk User - Pool Configuration .................................................................................... 13

Table 5: Kiosk User - Pool Settings ............................................................................................ 13

Table 6: Task Worker - Pool Configuration ................................................................................. 14

Table 7: Task Worker - Pool Settings ......................................................................................... 14

Table 8: Knowledge Worker - Pool Configuration ....................................................................... 15

Table 9: Knowledge Worker - Pool Settings ............................................................................... 15

Table 10: Power User - Pool Configuration ................................................................................ 16

Table 11: Power User - Pool Settings ......................................................................................... 16

Table 12: Nutanix CVM Resources ............................................................................................. 20

Table 13: Desktop Registry Policy Keys ..................................................................................... 20

Table 14: Desktop PCoIP Policy Parameters ............................................................................. 20

H

2

View on Nutanix | 25

About the Author

Steven Poitras is a Solution Architect on the Technical Marketing team at Nutanix, Inc. In this role, Steven helps design architectures combining applications with the Nutanix platform creating solutions helping solve critical business needs and requirements and disrupting the infrastructure space. Prior to joining Nutanix he was one of the key solution architects at the Accenture Technology Labs where he was focused on the Next Generation Infrastructure (NGI) and Next Generation Datacenter (NGDC) domains. In these spaces he has developed methodologies, reference architectures, and frameworks focusing on the design and transformation to agile, scalable, and cost-effective infrastructures which can be consumed in a service-oriented or cloud-like manner.

Follow Steven on Twitter at @StevenPoitras.

About Nutanix

Nutanix is the first company to offer a radically simple compute and storage infrastructure for implementing enterprise-class virtualization without complex and expensive external network storage (SAN or NAS). Founded in 2009 by a team that built scalable systems such as Google File System and enterprise-class systems such as Oracle Database/Exadata, Nutanix is based in San José, California, and is backed by Lightspeed Venture Partners, Khosla Ventures and Blumberg Capital.

Follow the Nutanix blogs at http://www.nutanix.com/blog/

Follow Nutanix on Twitter at @Nutanix

H

2

View on Nutanix | 26

H