Dell EMC Ready Architectures for VDI · Dell EMC Ready Architectures for VDI based on Dell EMC VxBlock System 1000 is a perfect solution for your high-performing VDI workloads. VxBlock

Dell EMC Ready Architectures for VDIDesigns for VMware Horizon 7 on VxBlock System 1000September 2019

H17849.2

Validation Guide

Abstract

This validation guide describes the architecture and performance of the integration ofVMware Horizon components for virtual desktop infrastructure (VDI) on Dell EMCVxBlock System 1000 converged infrastructure.

Dell EMC Solutions

Copyright © 2019 Dell Inc. or its subsidiaries. All rights reserved.

Dell believes the information in this publication is accurate as of its publication date. The information is subject to change without notice.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS-IS.” DELL MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH

RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS

FOR A PARTICULAR PURPOSE. USE, COPYING, AND DISTRIBUTION OF ANY DELL SOFTWARE DESCRIBED IN THIS PUBLICATION REQUIRES AN

APPLICABLE SOFTWARE LICENSE.

Dell Technologies, Dell, EMC, Dell EMC and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be the property of their

respective owners. Published in the USA.

Dell EMCHopkinton, Massachusetts 01748-91031-508-435-1000 In North America 1-866-464-7381www.DellEMC.com

2 Dell EMC Ready Architectures for VDI

Introduction 5Executive summary.............................................................................................6Document purpose..............................................................................................6Audience............................................................................................................. 7We value your feedback...................................................................................... 7

Test Environment Configuration and Best Practices 9Validated hardware resources........................................................................... 10Validated software resources............................................................................ 12Validated system version matrix........................................................................ 12Virtual networking configuration........................................................................12Management server infrastructure.................................................................... 13

NVIDIA GRID License Server................................................................ 13SQL Server databases.......................................................................... 13DNS...................................................................................................... 13

High availability..................................................................................................13VMware Horizon 7 architecture......................................................................... 14

Solution Performance and Testing 17Testing process................................................................................................. 18

Resource monitoring.............................................................................18Load generation....................................................................................19Profiles and workloads..........................................................................19Virtual Desktop Profile......................................................................... 23

Login VSI test results and analysis.................................................................... 23Login VSI Test Results Summary......................................................... 24Knowledge Worker, 100 users per host, ESXi 6.7, Horizon 7.7 ............ 25Power Worker, 81 users per host, ESXi 6.7, Horizon 7.7 ...................... 31Graphics Multimedia Worker, 44 users per host, ESXi 6.7, Horizon 7.7....36RDSH Task Worker, 173 users per host, ESXi 6.7, Horizon 7.7............. 42

Conclusion 47Density recommendations.................................................................................48Summary.......................................................................................................... 48

References 49Dell EMC documentation.................................................................................. 50VMware documentation....................................................................................50NVIDIA documentation..................................................................................... 50

Chapter 1

Chapter 2

Chapter 3

Chapter 4

Chapter 5

CONTENTS

Dell EMC Ready Architectures for VDI 3

Contents


CHAPTER 1

Introduction

This chapter presents the following topics:

l Executive summary................................................................................................................. 6l Document purpose.................................................................................................................. 6l Audience..................................................................................................................................7l We value your feedback.......................................................................................................... 7


Executive summary

Virtual desktop infrastructure (VDI) plays a crucial role in today's business transformationinitiatives. VDI is the most efficient way to present Microsoft Windows applications to end users intheir digital workspaces and provides a consistent user experience across user devices for themodern-day mobile workforce. Organizations increasingly rely on VDI to provide the agile, secure,and centrally-managed desktops that are so important for their workforce.

It can be challenging for organizations to set up VDI infrastructure. This is mainly because typicalVDI infrastructure involves the integration of multiple data center components such as storage,network, and compute. The multi-vendor profile of these components often creates deploymentand performance challenges if a system is not optimized for VDI. To consistently maintain a multi-component and multi-vendor environment with a specialized skill set is often challenging fororganizations and the effort to maintain a stable VDI infrastructure can have a negative impact ontotal cost of ownership (TCO).

Dell EMC Ready Architectures for VDI based on Dell EMC VxBlock System 1000 is a perfectsolution for your high-performing VDI workloads. VxBlock is the proven leader in convergedinfrastructure, providing enterprises worldwide with the simplicity of a turnkey experience thatallows them to focus on innovation rather than maintenance. The VxBlock 1000 combines industry-leading technologies—including powerful Dell EMC storage and data protection options, CiscoUCS blade and rack servers, Cisco LAN and SAN networking, and VMware virtualization—into onefully integrated system.

VxBlock 1000 is engineered according to your needs and takes the complexities out of componentintegration. It simplifies upgrades and daily operations, comes with converged management, and asimplified path to a cloud operating model—and all with single-call support. VxBlock 1000converged infrastructure system is a future-proof design that ensures your system can supportnext-generation technologies and meet performance, scalability, and simplicity requirements.

Dell EMC recommends VxBlock System 1000 converged infrastructure to run VMware Horizon 7VDI infrastructure. VMware Horizon 7 provides a streamlined approach to delivering and managingvirtual desktops and applications, providing a consistent user experience across devices andlocations while keeping corporate data secure and compliant. VxBlock 1000 provides a highlyscalable and agile platform to run your enterprise level VDI workloads. You can also run your VDIworkloads in combination with high-value applications or workloads like SAP, Oracle, MicrosoftSQL and Epic in a VxBlock 1000 system.

At Dell EMC, the Ready Architectures for VDI team tests the VDI solutions to ensure their validity.As part of the testing process, engineers tune the system to maximize performance and efficiency,and document best practices. Finally, a separate team of experts evaluate the test results toensure that the systems can be properly configured and sized for customers. In the validationeffort described in this guide, we have used the Login VSI tool, which is an industry standard toolfor benchmarking VDI workloads. We tested typical Login VSI workloads such as Task Worker,Knowledge Worker, Power Worker and Multimedia Worker with a desktop virtual machine (VM)profile tagged to that workload. This document includes a detailed analysis based on the testresults and recommends user density figures for these workloads that prioritize the best end-userexperience (EUE).

Document purpose

This validation guide details the architecture, components, testing methods, and test results forDell EMC VxBlock System 1000 with VMware Horizon 7. It includes the test environmentconfiguration and best practices for systems that have undergone testing.

Introduction


Audience

This guide is intended for architects, developers, and technical administrators of IT environments.It provides an in-depth explanation of the testing methodology and basis for VDI densities. It alsovalidates the Dell EMC Ready Architectures for VDI solution that deliver Microsoft Windows virtualdesktops to users of VMware Horizon 7 on Dell EMC VxBlock System 1000 convergedinfrastructure.

We value your feedback

Dell EMC and the authors of this document welcome your feedback on the solution and thesolution documentation. Contact the Dell EMC Solutions team by email or provide your commentsby completing our documentation survey.

Authors: Dell EMC Ready Architectures for VDI Team.

Note: The following page on the Dell EMC Communities website provides links to additionaldocumentation for VDI Ready Solutions: VDI Info Hub for Ready Solutions.

Introduction


mailto:[email protected]?subject=Feedback:%20Dell%20EMC%20Ready%20Architectures%20for%20VDI:%20Designs%20for%20VMware%20Horizon%207%20on%20VxBlock%201000%20VG%20(H17849.2)

https://www.surveymonkey.com/r/SolutionsSurveyExt

https://community.emc.com/docs/DOC-69231

Introduction


CHAPTER 2

Test Environment Configuration and BestPractices


l Validated hardware resources................................................................................................ 10l Validated software resources.................................................................................................12l Validated system version matrix.............................................................................................12l Virtual networking configuration............................................................................................ 12l Management server infrastructure.........................................................................................13l High availability...................................................................................................................... 13l VMware Horizon 7 architecture............................................................................................. 14


Validated hardware resourcesValidation of the architecture is limited to the specific hardware listed in this section.

Enterprise platforms

We used the Dell EMC VxBlock System 1000 converged infrastructure for this validation effort.The VxBlock 1000 offers the latest storage arrays from Dell EMC together with compute andnetworking equipment from Cisco Systems and the Advanced Management Platform (AMP)management infrastructure. The compute layer includes both Cisco UCS B-Series and C-SeriesServers. The storage layer includes multi-array support from Dell EMC VMAX All-Flash, Unity,PowerMax, XtremIO, and Isilon storage to fulfill both block and file storage needs. The VxBlock1000 comes with Cisco UCS Gen 3 and Gen 4 LAN and SAN networking options and can easily beexpanded by adding additional compute, network, and storage resources.

The testing completed for this document used a single-node Cisco Rack Mount server, the C240M5. This server is a 2-socket, 2 rack unit (2RU) rack server offering industry-leading performanceand expandability. It is well-suited for a wide range of enterprise workloads, including virtualization,high-performance applications, Big Data and Analytics. Cisco UCS C-Series Rack Servers can bedeployed as standalone servers or as part of a Cisco Unified Computing System (Cisco UCS)managed environment. Cisco's standards-based unified computing innovations help customersreduce their TCO and increase their business agility. The server supports GPU configurations thatrun graphic-intensive workloads.

We called the server configuration for this testing "C7". It is based on Intel's Xeon ScalableProcessors (codenamed "Skylake") with 768 GB of RAM. Configuration details are given in thefollowing table:

Table 1 Validated server hardware configurations for Cisco UCS C240 M5

Serverconfig

Enterpriseplatform

CPU Memory Storage BIOS HD config Network

C7 Cisco C240M5

2 x IntelXeon Gold6138 (20Core, 2.0GHZ)

768 GB @2666 MT/s(24 x 32 GBDDR4)

Cisco UCSVIC 1457Quad Port10/25GSFP28CNAMLOM(FibreChannel)

C240M5.4.0.2a.0

2 X 64 GB Cypressmirrored SD cards forhost hypervisor

Cisco UCSVIC 1457Quad Port10/25GSFP28CNAMLOM(FibreChannel)

Network hardware

The following network hardware was used in our test environment:

The Cisco UCS C240 M5 rack mount server is connected to the UCS Fabric Interconnects (FI).The FIs are connected northbound to Cisco Nexus switches for outside network connectivity. Forstorage connectivity, the FIs are connected to fabric switches with ports that also connect to theXtremIO SAN storage. The FIs are managed using Cisco UCS manager software. With Cisco UCSmanager, administrators can manage a multi-workload environment that includes infrastructure forVDI workloads.

l Two Cisco UCS FI 6454 Fabric Interconnects

l Two Cisco Nexus 9336C-FX2 switches for network connectivity

l Two Cisco MDS 9148S Multi-layer Fabric Switch for storage connectivity

Test Environment Configuration and Best Practices


Storage hardware

The following storage hardware was used in our test environment:

l XtremIO SAN with an X-Brick X2 all-flash storage array provided the storage for the VDIdesktops. The storage array had RAID 1 configuration with a LUN size of 10 TB.

l Two 64 GB mirrored SD cards were used for hypervisor hosting on the Cisco UCS C240 M5host server.

The XtremIO X2 storage platform is designed to support all modern virtual datacenter objectives.It provides up to 80 percent better response times for VDI without compromising efficiency andfour to 20 times data reduction using inline deduplication, compression, XtremIO Virtual Copies,and thin provisioning. XtremIO is well suited for mixed workloads, virtualized applications and VDI.With multi-dimensional scalability, in-memory metadata, unmatched storage efficiency, richapplication integrated copy services, metadata-aware replication, and unprecedented managementsimplicity, XtremIO delivers a simple, agile, scalable, fully virtualized datacenter while minimizinginfrastructure footprint and TCO. With a scale-out design, it is ideal for data reduction and copy-friendly workflows, such as VDI and test and development environments.

Graphics hardware

We used an NVIDIA Tesla P40 GPU for graphics workload testing. The Tesla P40 is a dual-slot10.5-inch PCI Express Gen3 graphics card featuring a single high-end NVIDIA Pascal GPU and atotal of 24 GB GDDR5 memory per card.

The NVIDIA Tesla P40 GPU accelerator works with NVIDIA Quadro vDWS software and is the firstsystem to combine an enterprise-grade visual computing platform for simulation, HPC rendering,and design with virtual applications, desktops, and workstations. This gives organizations thefreedom to virtualize both complex visualization and compute (CUDA and OpenCL) workloads. TheNVIDIA Tesla P40 uses of the industry-leading NVIDIA Pascal architecture. With 24 GB of framebuffer and 24 NVENC encoder sessions, this GPU card is highly recommended for running graphicintensive workloads.



Validated software resources

Dell EMC validated this solution with the software components listed in the following table.

Table 2 Validated software component versions

Component Description/Version

Hypervisor VMware ESXi 6.7

Broker technology VMware Horizon version 7.7

Broker database Microsoft SQL Server 2016

Management VM operatingsystem

Microsoft Windows Server 2016 (Connection Server and DB)

Virtual desktop operatingsystem

Microsoft Windows 10 Enterprise

Office application suite Microsoft Office Professional 2016

Login VSI test suite Version 4.1.32.1

Platform VxBlock 1000

NVIDIA GRID software (forgraphics testing)

7.2

Validated system version matrix

Validation of the architecture is limited to the specific version matrix listed in the following table.

Table 3 Version matrix for tested system

Serverconfiguration

NvidiavGPUversion

Hypervisor Hypervisorversion

Hypervisorbuild

Bios VxBlockversion

Windows10 version

Windows10patches

C7 n/a ESXi 6.7 1032608 C240M5.4.0.2a.0

RCM6.5.1.1

1803 -17134.523

KB4480966

C7 + 2x P40

Virtual networking configuration

The network configuration for the testing used two 25 GB ports on the Virtual Interface Card(VIC) 1457 that is connected to the Cisco Fabric Interconnects (FI). All required VLANs traversethrough a 25 Gbps VIC from the servers to the Fabric Interconnects.

We used the following VLAN configurations for the compute and management hosts in ourvalidation testing:

l Management VLAN: Configured for hypervisor infrastructure traffic—L3 routed via coreswitch.



l VDI VLAN: Configured for VDI session traffic—L3 routed via core switch.

Management server infrastructure

The management server component sizing recommendations for VxBlock 1000 are listed in thefollowing table. All management infrastructure VMs were hosted in an AMP-3S, a single systemmanagement infrastructure platform used to manage a single platform like VDI in a datacenter.

Table 4 Sizing for management server in VxBlock 1000

Component vCPU RAM (GB) NIC OS + data vDisk(GB)

VMware vCenter Appliance 4 16 1 250

Horizon Connection Server 2 8 1 40

SQL Server Standard 2 8 1 40+40+100

Remote File Server 2 8 1 40+200

NVIDIA GRID License ServerWhen using NVIDIA vGPU cards, graphics-enabled VMs must obtain a license from a GRID LicenseServer on your network.

We installed the GRID License Server software on a system running a Windows 2016 operatingsystem to test the vGPU configurations and made the following changes to address licensingrequirements:

l Used a reserved fixed IP address

l Configured a single MAC address

l Applied time synchronization to all hosts on the same network

SQL Server databases

During validation, a single dedicated SQL Server 2016 VM hosted the VMware databases in themanagement layer. We separated SQL data, logs, and tempdb into their respective volumes, andcreated a single database for Horizon Connection Server.

DNSDNS is the basis for Microsoft Active Directory and also controls access to various softwarecomponents for VMware services. All hosts, VMs, and consumable software components musthave a presence in DNS. We used a dynamic namespace integrated with Active Directory andadhered to Microsoft best practices.

High availability

Although we did not enable high availability (HA) during the validation that is documented in thisguide, we strongly recommend that HA be factored into any VDI design and deployment. Thisprocess follows the N+1 model with redundancy at both the hardware and software layers. Thedesign guide for this architecture provides additional recommendations for HA and is available atthe VDI Info Hub for Ready Solutions.




VMware Horizon 7 architecture

When designing and determining the architecture for a successful VDI deployment, it is importantto understand the underlying network traffic flows, ports, and components. Use Figure 1 as astarting reference for understanding the interdependencies of the different components within aVMware Horizon 7 architecture. The number of ports and protocols that are required will varydepending on the size of the deployment, the external connectivity requirements, and the displayprotocols in use (RDP, Blast, or PCoIP). You should undertake careful planning and design to allowthese ports and protocols in the corporate network firewall policies.

For more information about required ports and protocols, see VMware View ports and networkconnectivity requirements (1027217) and the VMware Horizon Reference Architecture guide.



https://kb.vmware.com/s/article/1027217

https://kb.vmware.com/s/article/1027217

https://techzone.vmware.com/resource/workspace-one-and-horizon-reference-architecture#sec9-sub2

Figure 1 VMware Horizon architecture





CHAPTER 3

Solution Performance and Testing


l Testing process......................................................................................................................18l Login VSI test results and analysis.........................................................................................23


Testing processTo ensure good EUE and cost-per-user, we conducted our testing on this solution using Login VSI,a load-generation tool that monitors both hardware resource utilization parameters and EUEduring load-testing.

For each user scenario, we ran the tests four times, once to validate data capture and three timesto collect metrics and analyze variance.

Our EUE validation consisted of logging into a session while the system was under a load createdby the Login VSI tool and completing tasks from the workload definition. While this test issubjective, it helps to provide a better understanding of the EUE in the desktop sessions,particularly under high load. It also helps to ensure reliable data gathering.

Resource monitoring

To ensure that the user experience was not compromised, we monitored the following importantresources:

l Compute host server resources—VMware vCenter (for solutions based on VMwarevSphere) or Microsoft Performance Monitor (for solutions based on Hyper-V) gather key data(CPU, memory, disk, and network usage) from each of the compute hosts during each testrun. This data was collected for each host and consolidated for reporting. We do not report anymetrics for the management host servers. However, they were monitored manually duringtesting to ensure that no bottlenecks impacted the test.

l Utilization thresholds—Resource overutilization can cause poor EUE. We monitored therelevant resource utilization parameters and compared them to relatively conservativethresholds. The thresholds were selected based on industry best practices and our experienceto provide an optimal trade-off between good EUE and cost-per-user while also allowingsufficient burst capacity for seasonal or intermittent spikes in demand.The following table shows the pass/fail thresholds that we set for our testing process:

Table 5 Pass/fail thresholds

Parameter Pass/fail threshold

Physical host CPU utilization 85% a

Physical host memory utilization 85%

Network throughput 85%

Storage I/O latency 20 milliseconds (ms)

Login VSI Failed Session 2%

a. The Ready Solutions for VDI team recommends that steady-state average CPU utilizationon the host should not exceed 85 percent in a production environment. Average CPUutilization sometimes exceeded our recommended percentage. Because of the nature ofautomated testing tools like Login VSI, a 5 percent margin of error was accepted and it doesnot impact our sizing guidance.

l GPU resources—We collected GPU utilization metrics from VMware vCenter.



Load generationLogin VSI from Login VSI, Inc. is the industry-standard tool for testing VDI environments andRDSH environments.

Login VSI installs a standard collection of desktop application software (including Microsoft Officeand Adobe Acrobat Reader) on each VDI desktop testing instance. It then uses a configurablelauncher system to connect a specified number of simulated users to available desktops within theenvironment. When the simulated user is connected, a login script configures the user environmentand starts a defined workload. Each launcher system can launch connections to several VDIdesktops (target machines). A centralized management console configures and manages thelaunchers and the Login VSI environment.

We used the following login and boot conditions:

l For most of our tests, new user sessions were logged in at a steady rate over a one-hourperiod. During tests of low-density solutions such as GPU and graphic-based configurations,users were logged in every 10 seconds.

l All desktops were started before users logged in.

l All desktops ran an industry-standard anti-virus solution. Windows 10 machines used WindowsDefender.

Profiles and workloadsThe combination of virtual desktop profiles and simulated user workloads determines the totalnumber of users (user density) that the VDI solution can support. Each virtual desktop profile anduser workload is defined by specific metrics and capabilities. It is important to understand theseterms in the context of this document.

Profiles and workloads are defined as follows:

l Profile—The configuration of the virtual desktop: the number of vCPUs and the amount ofRAM that is configured on the desktop and available to the user

l Workload—The set of applications and tasks that are defined to be used by a simulated user inthe test

Load-testing on each machine profile is carried out using an appropriate user workload that isrepresentative of the relevant use case. Typical profiles and their associated workloads aresummarized in the following table:

Table 6 Virtual desktop profile to workload mapping

Profile name Workload name

Knowledge Worker Login VSI Knowledge Worker

Power Worker Login VSI Power Worker

Graphics Multimedia Worker Login VSI Multimedia Worker

RDSH Task Worker Login VSI Task Worker



Typical Login VSI workloads are summarized in the following table. For additional information, seethe Login VSI website.

Table 7 Login VSI workloads

Workload name Workload description

Login VSIKnowledge Worker

Designed for virtual machines with 2 vCPUs. This workload includes the following activities:

l Microsoft Outlook—Browse messages.

l Internet Explorer—Browse websites and open a YouTube style video (480p movie trailer)three times in every loop.

l Word—Start one instance to measure response time and another to review and edit adocument.

l Doro PDF Printer and Acrobat Reader—Print a Word document and export it to PDF.

l Excel—Open a large randomized sheet.

l PowerPoint—Review and edit a presentation.

l FreeMind—Run a Java-based Mind Mapping application.

l Other—Perform various copy and zip actions.

Login VSI PowerWorker

The most intensive of the standard Login VSI workloads. The following activities areperformed with this workload:

l Begin by opening four instances of Internet Explorer and two instances of Adobe Readerthat remain open throughout the workload.

l Perform more PDF printer actions than in the other workloads.

l Watch a 720p and a 1080p video.

l Reduce the idle time to two minutes.

l Perform various copy and zip actions.

Login VSIMultimedia Worker(Graphicsperformanceconfiguration)

A workload that is designed to heavily stress the CPU when using software graphicsacceleration. GPU-accelerated computing offloads the most compute-intensive sections ofan application to the GPU while the CPU processes the remaining code. This modifiedworkload uses the following applications for its GPU/CPU-intensive operations:

l Adobe Acrobat

l Google Chrome

l Google Earth

l Microsoft Excel

l HTML5 3D spinning balls

l Internet Explorer

l MP3

l Microsoft Outlook

l Microsoft PowerPoint

l Microsoft Word

l Streaming video



https://www.loginvsi.com/documentation/index.php?title=Login_VSI_Workloads

Table 7 Login VSI workloads (continued)

Workload name Workload description

Login VSI TaskWorker

The least intensive of the standard workloads. It runs fewer applications and starts and stopsthem less frequently than the other workloads, resulting in lower CPU, RAM and I/O usage.The Task Worker workload uses the following applications:

l Adobe Reader

l Microsoft Excel

l Internet Explorer

l Microsoft Outlook

l Microsoft Word

l Print and zip actions using Notepad and 7-zip



A comparison of linked clones and instant clones

Horizon supports two provisioning methods that deliver space-optimized virtual desktop pools:linked clones and instant clones. For this testing we have used instant clones to create virtualmachines. The user density per host is not impacted by using one over the other. The differencesin the test graphs for these two methods are a result of the following processes:

l For linked clones, all the VMs are re-booted before the test starts to simulate a boot storm.The CPU spike during the boot storm phase is due to the CPU being utilized by all VMs duringpowering on. Once the VMs are booted up, CPU utilization comes down to near zero as shownin the following figure. During the logon phase CPU utilization again increases and once allusers have logged in CPU utilization remains constant as shown in the steady state phase inthe figure. Once the steady state phase is over and users start to log off, CPU utilizationdecreases and dips to near zero when all users log off.

Figure 2 Host CPU utilization for linked clones

l For instant clones, the VMs are re-booted after the session ends because when a user logs outof the instant clone, the clone is destroyed and re-created for the next user. CPU utilizationgradually increases during the log on phase when users start logging in and then remainsconstant during the steady state phase when logins have been completed, as shown in thefollowing figure. Once the steady state period is over and users starts to log off, CPUutilization again decreases and reaches near zero when all users have logged off. After userlogoff the instant clone pool is re-created. During this phase there is a CPU spike that thendrops to near zero when pool re-creation is complete.



Figure 3 Host CPU utilization for instant clones

Virtual Desktop Profile

The following table summarizes the profiles or Desktop VM configurations for the workloads thatwe tested.

Table 8 Desktop VM specifications

Profile name Workload name vCPUsa Configuredmemoryb

Reservedmemoryc

Screenresolution

Operating system

KnowledgeWorker

Login VSIKnowledgeWorker

2 4 GB 2 GB 1920 x1080

Windows 10Enterprise 64-bit

Power Worker Login VSI PowerWorker

4 8 GB 4 GB 1920 x1080


GraphicsMultimediaWorker

Login VSIMultimediaWorker

4 8 GB 8 GB 1920 x1080


RDSH TaskWorker

Login VSI TaskWorker

8 32 GB 32 GB 1280 x 720 Windows 2016 64-bit

a. The number of virtual CPUs assigned to the desktop virtual machineb. Memory configured or assigned to the desktop virtual machinec. Amount of memory reserved for the virtual machine. Reserved memory is guaranteed

Login VSI test results and analysis

We used the Login VSI test suite to simulate the user experience for several profile types underthe typical workload for that type. We performed the testing on a single node C240 M5 rackmount server on VxBlock System 1000 converged infrastructure using the C7 host hardwareconfiguration shown in the following table.



Table 9 Configuration details

Serverconfiguration

Enterpriseplatform

CPU Memory Storage BIOS HD config Network

C7 Cisco C240M5

2x IntelXeon Gold6138 (20Core, 2.0GHZ)

768 GB@2666MT/s(24x32 GBDDR4)

Cisco UCSVIC 1457Quad Port10/25GSFP28 CNAMLOM(FibreChannel)

C240M5.4.0.2a

2 X 64 GBCypress mirroredSD cards for hostHypervisor

Cisco UCSVIC 1457Quad Port10/25GSFP28 CNAMLOM(FibreChannel)

Login VSI Test Results Summary

Before we look into a detailed analysis for each virtual desktop profile or workload tested, let uslook at a summary of the results as shown in the following table.

Table 10 Login VSI test results summary

Serverconfiguration

Profile name RemoteDisplayProtocol

Workloadname

Userdensity

AverageCPU

Averageactivememory

AverageIOPS peruser

C7 KnowledgeWorker

PCOIP Login VSIKnowledgeWorker

100 85.37 % 105 GB 17.29

C7 PowerWorker

PCOIP Login VSIPowerWorker

81 85.24 % 142 GB 23.19

C7 + 2x NvidiaTesla P40

GraphicsMultimediaWorker(Virtual PC:P40-1B)

BlastExtreme

Login VSIMultimediaWorker

44 85.26 % 360 GB 67.31

C7 RDSH TaskWorker

BlastExtreme

Login VSITask Worker

173(HorizonAppsRDSH/PublishedDesktop)

84.98 % 73 GB 10.93

The table headings are defined as follows:

l Server configuration—The configuration used for this validation effort. See Table 9 forconfiguration details.

l Profile name—The configuration of the virtual desktop, including the number of vCPUs andthe amount of RAM that is configured on the desktop and available to the user.

l Workload name—The set of applications and tasks defined to be used by a simulated user.See Table 7 for the details of workloads tested in this testing.



l User density—The number of users per compute host that successfully completed theworkload test within the acceptable resource limits for the host. For clusters, this numberreflects the average per server density achieved for all compute hosts in the cluster.

l Average CPU—The average CPU usage over the steady-state period. For clusters, thisnumber represents the combined average CPU usage of all compute hosts. On the latest Intelprocessors, the ESXi host CPU metrics exceed the rated 100 percent for the host if TurboBoost is enabled (the default setting). An additional 35 percent of CPU is available from theTurbo Boost feature, but this additional CPU headroom is not reflected in the VMware vSpheremetrics where the performance data is gathered.

l Average active memory—For ESXi hosts, the amount of memory that is actively used, asestimated by the VM kernel based on recently accessed memory pages. For clusters, this is theaverage amount of guest physical memory that is actively used across all compute hosts overthe steady-state period.

l Average IOPS per user—IOPS calculated from the average disk IOPS over the steady stateperiod divided by the number of users.

Knowledge Worker, 100 users per host, ESXi 6.7, Horizon 7.7This section describes the metrics that we collected and analyzed for this use case.

CPU usage

The following figure shows the performance data for 100 user sessions on the VxBlock computehost when tested with the Login VSI Knowledge Worker workload.

During the login phase, CPU utilization increased steadily until all logins were complete. During thesteady state phase, CPU utilization reached a steady state average of 85.38 percent on thecompute host. This value is close to the pass/fail threshold we set for average CPU utilization—see Table 5. To maintain a good EUE it is essential that this threshold is not exceeded. You canload more user sessions while exceeding the designated threshold for CPU utilization but thismight result in a degradation in user experience. CPU utilization reached its peak during user logoffand the re-creation of instant clones and then decreased to a minimum value.

Figure 4 CPU utilization on the compute node



Memory

As shown in the following figure, a consumed memory of 133 GB was recorded before the testingstarted. This was because all VMs were already powered on before user sessions were loaded.Memory consumption increased during the login phase. During the steady state phase, consumedmemory reached an average of 299 GB on the compute host. With a total memory of 768 GBavailable on the compute host, memory was not a constraint during the testing.

Figure 5 Consumed memory utilization on the compute node

Active memory usage increased steadily during the login phase. During the steady state phase,active memory remained almost constant and recorded an average steady active memory of 105GB. This indicates that during the steady state phase, memory was not a concern and there wasenough memory available in the ESXi host cluster to meet requirements. During user logoff and there-creation of instant clones, a peak active memory of 371 GB was recorded on the compute host.In this phase the desktop VMs which get logged off are deleted and re-created again usingVMware Horizon instant clone technology. This is a memory intensive task. However, no memoryballooning or swapping occurred on any of the hosts during the testing process, indicating nomemory constraints in the cluster.



Figure 6 Active memory utilization on the compute node

Network usage

Network bandwidth was not an issue during testing. Network bandwidth usage steadily increasedduring the logon phase and network utilization recorded a peak of 176 Mbps during the steadystate phase. An average network usage of 136 Mbps was recorded by the compute host during thesteady state operations. With two 25 GbE network interface controllers (NICs) configured as anuplink in an active/active team, network bandwidth usage was well under the 85 percent thresholdset for network throughput.

Figure 7 Network usage on the compute host

IOPS

The following figure shows the disk IOPS numbers for the Dell EMC XtremIO storage datastore.Cluster IOPS reached a peak of 24,211 during user logoff and the instant clone re-creation process.



The re-creation of instant clones is storage IOPS intensive due to the creation of VMware swapand difference disk files for the newly created desktop VMs.

The steady state IOPS maximum value was 5,149. Average cluster disk IOPS during the steadystate phase was 1,729. Based on these numbers, the average disk IOPS per session during thesteady state phase was 17.29. You can select your disk specifications in accordance with this IOPSfigure in your sizing exercise. I/O latency during the steady state phase was 0.17 ms. The lowlatency figure indicates that storage resources were not a bottleneck during steady stateoperations.

Figure 8 Datastore IOPS utilization

Storage I/O latency

The XtremIO datastore I/O latency reached a peak of 0.59 ms during the re-creation of instantclones. A peak in latency was expected due to the creation of the new swap files and differencedisks required for the instant clone VMs as these tasks are disk I/O intensive. Average clusterlatency during the steady state phase was 0.17 ms. This value is well below the pass/fail thresholdof 20 ms set for storage I/O latency. Overall, storage resources did not appear to be a bottleneckduring testing.



Figure 9 Latency in the XtremIO datastore

Login VSI user experience summary

The baseline score for the Login VSI test was 965. This score falls within the 800-1199 range ratedas "Good" by the Login VSI tool. For more information about Login VSI baseline ratings andbaseline calculations, see this Login VSImax article. The Login VSI test was run for 100 usersessions for the Login VSI Knowledge Worker workload. As indicated by the blue line in thefollowing figure, the system reached a VSImax average score of 1,192 when 100 sessions wereloaded. This is well below the VSI threshold score of 1,966 set by the Login VSI tool. During theduration of testing VSImax was never reached, which normally indicates a stable system and abetter user experience. See Table 11 for an explanation of the Login VSI metrics discussed here.

We noted that there were no failed sessions during testing. This indicates that the logon and logoffprocesses were smooth. When manually interacting with the sessions during the steady statephase, the mouse and window movement was responsive and video playback was good. Moreover,all the parameters we monitored were within the pass/fail thresholds outlined in Table 5. Thisindicates that there were no resource constraints on the system and system performance wasgood.



https://support.loginvsi.com/hc/en-us/articles/115004421905-VSImax-baseline-scores

Figure 10 Login VSI Graph Summary

The following table describes the Login VSI metrics.

Table 11 Login VSI metrics

Login VSI metrics Description

VSImax VSImax shows the number of sessions thatcan be active on a system before the systemis saturated. It is the point where the VSImaxV4 average graph line meets the VSImax V4threshold graph line. The intersection isindicated by a red X in the Login VSI graph.This number gives you an indication of thescalability of the environment (higher isbetter).

VSIbase VSIbase is the best performance of thesystem during a test (the lowest responsetimes). This number is used to determinewhat the performance threshold will be.VSIbase gives an indication of the baseperformance of the environment (lower isbetter).

VSImax v4 average VSImax v4 average is calculated on thenumber of active users that are logged ontothe system but removes the two highest andtwo lowest samples to provide a moreaccurate measurement.

VSImax v4 threshold VSImax v4 threshold indicates at which pointthe environment's saturation point is reached(based on VSIbase).

The following table gives the Login VSI score summary for the Knowledge Worker workload.



Table 12 Login VSI score summary

VSIbase VSImax average VSImax threshold VSImax reached

965 1,192 1,966 No

Power Worker, 81 users per host, ESXi 6.7, Horizon 7.7This section describes the metrics that we collected and analyzed for this use case.

CPU usage

The following figure shows the performance data for 81 user sessions on the VxBlock computehost when tested with the Login VSI Power Worker workload. With all user VMs powered onbefore starting the test, CPU usage was approximately 3 per cent. During the login phase CPUutilization increased steadily until all of the logins were complete. During the steady state phase,CPU utilization reached a steady state average of 85.24 percent on the compute host. This value isclose to the pass/fail threshold we set for average CPU utilization—see Table 5. To maintain agood EUE it is essential that this threshold is not exceeded. You can load more user sessions whileexceeding the designated threshold but this might result in a degradation in user experience. CPUutilization reached its peak during user logout and the re-creation of instant clones and thendecreased to a minimum value.


Memory

As shown in the following figure, a consumed memory of 396 GB was recorded before the testingstarted. This was because all VMs were already powered on before user sessions were loaded.Memory consumption increased during the login phase. During the steady state phase, consumedmemory reached a maximum of 588 GB on the compute host. With a total memory of 768 GBavailable on the compute host, memory was not a constraint during the testing.




Active memory usage increased steadily during the login phase. During the steady state phase,active memory remained almost constant and recorded an average steady active memory of 142GB. This indicates that during the steady state phase, memory was not a concern and there wasenough memory available in the ESXi host cluster to meet requirements. During user logout andthe re-creation of instant clones, a peak active memory of 588 GB was recorded on the computehost. In this phase the desktop VMs which gets logged off are deleted and re-created again usingVMware Horizon instant clone technology. This is a memory intensive task. However, no memoryballooning or swapping occurred on any of the hosts during the testing process, indicating nomemory constraints in the cluster.




Network usage

Network bandwidth was not an issue during testing. Network bandwidth usage steadily increasedduring the login phase. Network utilization recorded a peak of 261 Mbps during the steady statephase. An average network usage of 224 Mbps was recorded by the compute host during thesteady state operations. With two 25 GbE NICs configured as an uplink in an active/active team,network bandwidth usage was well under the 85 percent threshold set for network throughput.Network utilization reached a peak of 269 Mbps during logout and the re-creation of clones.


IOPS

The following figure displays the disk IOPS figure for the Dell EMC XtremIO storage datastore.Cluster IOPS reached a peak of 27,744 during logout and the instant clone re-creation process.The re-creation of instant clones is storage IOPS intensive due to the creation of VMware swapand difference disk files for the newly created desktop VMs.





Storage I/O latency

The XtremIO datastore I/O latency reached a peak of 0.46 ms during the re-creation of InstantClones. A peak in latency was expected due to the creation of new swap files and difference disksrequired for the Instant Clone VMs. These tasks are disk I/O intensive. Average cluster latencyduring steady state was 0.17 ms. This value is well below the pass/fail threshold of 20 ms set forstorage I/O latency. Overall, storage resources did not appear to be a bottleneck during thistesting.





The baseline score for the Login VSI test was 907. This score falls in the 800-1199 range rated as"Good" by the Login VSI tool. For more information about Login VSI baseline ratings and baselinecalculations, see this Login VSImax article. The Login VSI test was run for 81 user sessions for theLogin VSI Power Worker workload. As indicated by the blue line in the following figure, the systemreached a VSImax average score of 1,154 when 81 sessions were loaded. This is well below the VSIthreshold score of 1,908 set by the Login VSI tool. During the duration of testing VSImax wasnever reached, which normally indicates a stable system and a better user experience. See Table 11for an explanation of the Login VSI metrics discussed here.

We noted that there were no failed sessions during testing. This indicates that the login and logoutprocesses were smooth. When manually interacting with the sessions during steady state, themouse and window movement was responsive and video playback was good. Moreover, allparameters we monitored were within the pass/fail threshold limit outlined in Table 5. Thisindicates there were no resource constraints on the system and the performance of the systemwas good.





The following table gives the Login VSI score summary for the Power Worker workload.



907 1,154 1,908 No

Graphics Multimedia Worker, 44 users per host, ESXi 6.7, Horizon 7.7This section describes the metrics that we collected and analyzed for this use case.

CPU usage

The graph shows the performance data for 44 user sessions on the VxBlock compute host whentested with the Login VSI Multimedia Worker workload.

As shown in the following figure, during the login phase CPU utilization increased steadily until alllogins were complete. During the steady state phase, CPU utilization reached a steady stateaverage of 85.26 percent on the compute host. This value is close to the pass/fail threshold wehave set for average CPU utilization—see Table 5. To maintain a good EUE it is essential that thisthreshold is not exceeded. You can load more user sessions while exceeding the designatedthreshold for CPU utilization but this might result in a degradation in user experience. CPUutilization reached its peak during user logout and the re-creation of instant clones and thendecreased to a minimum value.




GPU usage

We gathered the GPU metrics from the vSphere Web Client. The graphics intensive Login VSImultimedia workload was used for this testing. There were two NVIDIA P40 GPU cards configuredon the compute host. The GPU usage during the steady state phase on the two GPU cardsaveraged approximately 22 percent. The GPUs were leveraged for executing graphics intensivetasks, thus taking load off the CPUs and providing a better user experience.

Figure 19 GPU utilization on the compute node



Memory

As shown in the following figure, a consumed memory of 371 GB was recorded before the testingstarted. This was because all of the VMs were already powered on before the user sessions wereloaded. During the steady state phase, consumed memory remained constant at approximately 371GB. With a total memory of 768 GB available on the compute host, memory was not a constraintduring the testing.


During user login and the steady state phase, active memory remained almost constant andrecorded an average steady active memory of 360 GB. With 768 GB of memory available on thehost, memory was not a concern and there was enough memory available in the ESXi host clusterto meet requirements. No memory ballooning or swapping occurred on any of the hosts during thetesting process, indicating no memory constraints in the cluster.




Network usage

Network bandwidth was not an issue during testing. Network bandwidth usage steadily increasedduring the login phase. An average network usage of 137 Mbps was recorded by the compute hostduring the steady state operations. Network utilization reached a peak of 221 Mbps during thestart of the steady state period. With two 25 GbE NICs configured as an uplink in an active/activeteam, network bandwidth usage was well under the 85 percent threshold set for networkthroughput.


IOPS

The following figure shows the disk IOPS figure for the Dell EMC XtremIO storage datastore.Cluster IOPS reached a peak of 22,403 during user log out and the instant clone re-creation



process. The re-creation of instant clones is storage IOPS intensive due to the creation of VMwareswap and difference disk files for the newly created desktop VMs.



Storage I/O latency

The XtremIO datastore I/O latency reached a peak of 0.76 ms during the re-creation of instantclones. A peak in latency was expected due to the creation of new swap files and difference disksrequired for the instant clone VMs as these tasks are disk I/O intensive. Average cluster latencyduring the steady state phase was 0.18 ms. This value is well below the pass/fail threshold of 20ms set for storage I/O latency. Overall, storage resources did not appear to be a bottleneck duringthis testing.





The baseline score for the Login VSI test was 1,002. This score falls in the 800-1199 range rated as"Good" by the Login VSI tool. For more information about Login VSI baseline ratings and baselinecalculations, see this Login VSImax article. The Login VSI test was run for 44 user sessions for theLogin VSI Multimedia Worker workload. As indicated by the blue line in the following figure, thesystem reached a VSImax average score of 1,576 when 44 sessions were loaded. This is well belowthe VSI threshold score of 2,002 set by the Login VSI tool. During the duration of testing VSImaxwas never reached, which normally indicates a stable system and a better user experience. SeeTable 11 for an explanation of the Login VSI metrics discussed here.

We noted that there were no failed sessions during testing. This indicates that the login and logoutprocess were smooth. When manually interacting with the sessions during the steady state phase,the mouse and window movement was responsive and video playback was good. Moreover, allparameters we monitored were within the pass/fail threshold limit shown in Table 5. This indicatesthat there were no resource constraints on the system and system performance was good.


The following table shows the Login VSI score summary for the Multimedia Worker workload.






1,002 1,576 2,002 No

RDSH Task Worker, 173 users per host, ESXi 6.7, Horizon 7.7This section describes the metrics that we collected and analyzed for this use case.

CPU usage

The following figure shows the performance data for 173 Remote Desktop Session Host (RDSH)user sessions on the VxBlock compute host. The testing was carried out with the Login VSI TaskWorker workload. The compute host was populated with a Horizon Apps application pool of fiveRDSH VMs, which were used to supply the remote desktop sessions for this test. RDSH VMs areinstalled with the Windows 2016 Server operating system. We used the VMware Blast Extremedisplay protocol.

With all RDSH VMs powered on before testing started, the CPU usage was approximately 1percent. As shown in the following figure, during the login phase, CPU utilization increased steadilyuntil all logins were complete. During the steady state phase, CPU utilization reached a steadystate average of 84.98 percent on the compute host. This value is below the pass/fail thresholdthat we set for average CPU utilization, which includes a margin of 5 percent. See Table 5 for thethresholds we set. To maintain a good EUE, it is essential that this threshold is not exceeded. Youcan load more user sessions while exceeding the designated threshold we set for CPU utilization,but this might result in a degradation in user experience. CPU utilization dropped to almost zeroonce all users had logged out.


Memory

As shown in the following figure, consumed memory before testing started was recorded at 138GB. This was because all RDSH VMs were already powered on before the loading of user sessions.Memory consumption remained constant during the login phase. During the steady state phase,consumed memory reached an average of 141 GB on the compute host. With a total memory of768 GB available on the compute host, memory was not a constraint during the testing.




Active memory usage increased steadily during the login phase. During the steady state phase,active memory remained almost constant and an average steady active memory of 73 GB wasrecorded. This indicates that during the steady state phase, memory was not a concern and therewas enough memory available in the ESXi host cluster to meet requirements. During the userlogout phase, a peak active memory of 127 GB was recorded on the compute host. No memoryballooning or swapping was recorded on the host during the entire testing process, which indicatesthat memory was not a constraint in the cluster.




Network usage

Network bandwidth was not an issue during testing. Usage steadily increased during the loginphase and network utilization recorded a peak of 252 Mbps at the end of this phase. A peak of 249Mbps was recorded during the steady state phase. The steady state average was 222 Mbps. Withan available bandwidth of 2 x 25 Gbps on the VIC, network bandwidth usage was well under the 85percent threshold set for network throughput.


IOPS

The following figure displays the disk IOPS figure for the Dell EMC XtremIO storage data store.Cluster IOPS reached a peak of 26,608 during the logout phase. The steady state IOPS maximumvalue was 6,995 and the average cluster disk IOPS during the steady state phase was 1,892. Basedon these numbers, the average disk IOPS per session during the steady state phase was 10.93. Youcan select your disk specifications in accordance with this IOPS figure in your sizing exercise. Asshown in Figure 31, I/O latency during the steady state phase was 0.24 ms. The low latency figureindicates that storage resources were not a bottleneck during steady state operations.



Figure 30 Data store IOPS utilization

Storage I/O latency

The XtremIO data store I/O latency reached a peak of 0.97 ms during the logout phase. During thesteady state phase, the latency reached a peak of 0.3 ms. Average cluster latency during thesteady state phase was 0.24 ms, a value that is well below the pass/fail threshold of 20 ms that weset for storage I/O latency. Overall, storage resources did not prove to be a bottleneck during thistesting.

Figure 31 Latency in the XtremIO data store




The baseline score for the Login VSI test was 696. This score falls in the 0 to 799 range rated as'Very Good' by the Login VSI tool. For more information about Login VSI baseline ratings andbaseline calculations, see this Login VSImax article. The Login VSI test was run for 173 usersessions for the Login VSI Task Worker workload. As indicated by the blue line in the followingfigure, the system reached a VSImax average score of 1,544 when 173 sessions were loaded. Thisis well below the VSI threshold score of 1,966 set by the Login VSI tool. For the duration of testing,VSImax was never reached, which normally indicates a stable system and a better user experience.See Table 11 for an explanation of the Login VSI metrics discussed here.

We also noted that there were no failed sessions during testing. This indicates that the login andlogout processes were smooth. When manually interacting with the sessions during the steadystate phase, the mouse and window movement was responsive and video playback was good.Moreover, all the parameters we monitored were within the pass/fail threshold limit shown inTable 5. This indicates that there were no resource constraints on the system and systemperformance was good.


The following table shows the Login VSI score summary for the RDSH Task Worker workload:



696 1,544 1,696 No




CHAPTER 4

Conclusion

l Density recommendations..................................................................................................... 48l Summary............................................................................................................................... 48


Density recommendations

The following table lists the configurations that we tested with Microsoft Windows 10, MicrosoftWindows Server 2016, and Microsoft Office 2016. The table lists the user densities that werecommend based on our testing.

Table 16 Tested configurations and user density recommendations

Server configuration Profile Workload User density (per host)

C7 Knowledge Worker Login VSI KnowledgeWorker

100

C7 Power Worker Login VSI Power Worker 81

C7 + 2x Tesla P40 Graphics MultimediaWorker (Virtual PC:P40-1B)

Login VSI MultimediaWorker

44

C7 RDSH Task Worker Login VSI Task Worker 173 (Horizon Apps RDSH/Published Desktop)

Summary

The VxBlock System 1000 converged infrastructure platform provides a highly scalable andresilient system for VDI workloads along with exceptional user experience. Analysis of the resultshave shown that storage, network and memory were not a bottleneck during the testing weperformed with the C7 configuration. However, CPU utilization was close to the threshold we setand was a decisive factor in recommending the user densities outlined in this document. The LoginVSI results shows that VSI Max never reached the VSI threshold for any of the workloads tested,which indicates a stable system with excellent EUE.

The configurations for the VxBlock System 1000 converged infrastructure have been optimized forVDI. We selected the memory and CPU configurations that provide optimal performance. You canchange these configurations to meet your own requirements, but you should be aware thatchanging the memory and CPU configurations from those that have been validated in thisdocument will affect the user density per host.

With the introduction of the six-channels-per-CPU requirement for Skylake processors, the C7memory configuration recommendation has increased from the previous guidance of 512 GB to768 GB. This change was necessary to ensure a balanced memory configuration and optimizedperformance for your VDI solution. The additional memory is advantageous, considering theresulting increase in operating system resource utilization and the enhanced experience for userswhen they have access to additional memory allocations.

With a flexible choice of fully integrated Dell EMC storage and data protection, Cisco UCS serversand networking options backed by VMware virtualization, the VxBlock 1000 platform provides thecapability to run an enterprise level VDI environment. VxBlock 1000 is also capable of running amulti-workload environment that includes VDI and high-value applications, data analytics and soon.

Conclusion


CHAPTER 5

References


l Dell EMC documentation.......................................................................................................50l VMware documentation........................................................................................................ 50l NVIDIA documentation..........................................................................................................50


Dell EMC documentationThe following Dell EMC documentation provides additional and relevant information. Access tothese documents depends on your login credentials. If you do not have access to a document,contact your Dell EMC representative. Also see the VDI Info Hub for Ready Solutions for acomplete list of VDI resources.

l Dell EMC Virtual Desktop Infrastructure

This document is part of the documentation set for this architecture, which includes the following:

l Dell EMC Ready Architectures for VDI: Designs for VMware Horizon 7 on VxBlock System 1000Validation Guide

l Dell EMC Ready Architectures for VDI Designs for VMware Horizon 7 on VxBlock System 1000Design Guide

VMware documentation

The following VMware documentation provides additional and relevant information:

l VMware vSphere documentation

l VMware Horizon 7 documentation

l Best Practices for Published Application and Desktops in VMware Horizon Apps and VMwareHorizon 7

l VMware Compatibility Guide

l VMware Workspace ONE and VMware Horizon Reference Architecture

NVIDIA documentation

The following NVIDIA documentation provides additional and relevant information:

l NVIDIA Virtual GPU Software Quick Start Guide

References



https://www.dellemc.com/en-us/solutions/vdi/index.htm

https://www.dellemc.com/resources/en-us/asset/technical-guides-support-information/solutions/h17849-vxblock-horizon-validation-guide.pdf

https://www.dellemc.com/resources/en-us/asset/technical-guides-support-information/solutions/h17849-vxblock-horizon-validation-guide.pdf

https://www.dellemc.com/resources/en-us/asset/technical-guides-support-information/solutions/h17855-vxblock-horizon-design-guide.pdf

https://www.dellemc.com/resources/en-us/asset/technical-guides-support-information/solutions/h17855-vxblock-horizon-design-guide.pdf

https://docs.vmware.com/en/VMware-vSphere/index.html

https://docs.vmware.com/en/VMware-Horizon-7/index.html

https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/techpaper/vmware-horizon-7-apps-published-applications-desktops-best-practices.pdf

https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/techpaper/vmware-horizon-7-apps-published-applications-desktops-best-practices.pdf

https://www.vmware.com/resources/compatibility/search.php?deviceCategory=vsan&details=1&vsan_type=vsanreadynode&vsan_partner=23&vsan_releases=278&page=1&display_interval=10&sortColumn=Partner&sortOrder=Asc

https://techzone.vmware.com/resource/workspace-one-and-horizon-reference-architecture#component-design-horizon-architecture

http://docs.nvidia.com/grid/latest/grid-software-quick-start-guide/index.html

Documents

Dell EMC Ready Architectures for VDI · Dell EMC Ready Architectures for VDI based on Dell EMC VxBlock System 1000 is a perfect solution for your high-performing VDI workloads. VxBlock