BUILDING THE RIGHT INFRASTRUCTURE FOR VDI

Transcription

1 BUILDING THE RIGHT INFRASTRUCTURE FOR VDI Doing it right! #ILTACON #ILTA145

2 LISA STONE Client Systems Architect Cornerstone.IT

3 WHAT S UNDER THE HOOD?

4 Real World Remediation XenApp deployment built to support 350 users WHAT S WRONG WITH THIS PICTURE? 2 Physical Servers CPU 4 8 core 2.01 Ghz Memory 128 GB Hard Drives GB SAS Drives 2 Virtual Servers CPU 8 Memory 20 GB Storage on Nimble SAN

5 HYPERVISORS VDI Hosts Segregation CPU Are 10 core 2.50 GHZ processors better than 8 core 3.1 GHZ processors? Memory

6 TRAFFIC Network Traffic Separate PVS streaming traffic from network traffic PVS on same cluster / hosts as VDI machines

7 IOPS.. IOPS.. IOPS Write Cache IO Storage PVS Ram Cache PVS Ram Cache overflow to disk

8 Real World Remediation XenApp deployment built to support 350 users WHAT S WRONG WITH THIS PICTURE? 2 Physical Servers CPU 4 8 core 2.01 Ghz Memory 128 GB Hard Drives GB Sas Drives 2 Virtual Servers CPU 8 Memory 20 GB Storage on Nimble SAN

9 Post Remediation CURRENTLY SUPPORTS 360 PLUS USERS 3 Physical Servers CPU 2 Original Servers 4 8 core 2.01 Ghz 1 new server 2 12 core 2.7 Ghz Memory 128 GB 268GB per host Fusion IO Cards for Write Cache Virtualized all servers on VMWare Total - 18 Virtual Servers CPU 8 Memory 35 GB Storage on Fusion io card.

10 LOAD TEST Don t trust your vendor to spec out your hardware.. Prove it to yourself

11 JAMES HOPKINS Senior PS Consultant LoginVSI

12 LOAD TEST

13 LOGIN VSI : THE INDUSTRY STANDARD white papers 1

14 14 THE VDI LIFECYCLE

15 Phase I: Test and Validate Right Size your environment Mitigate Risk Raise Efficiency No surprises on Day 1 Identify potential bottlenecks Discover potential incompatibilities Deploy with Confidence

16 Phase II: Deploy With Confidence Automate everything Reduce opportunity for human error Deploy faster Consistent configuration of all servers Componentize one size doesn t fit all Reduce cost of IT

17 Phase III: Monitor and Alert Can users get to their VDI Desktop? Is VDI performance at levels we expected? Does performance stay consistent all day long? Are there performance trends that need to be addressed?

18 Phase IV: Automate your Lab Environment Test without impacting production Evaluate different vendor offerings Pilot changes to address trends in Production

19 WINDOWS 7 VS WINDOWS 10: TESTED WITH LOGON VSI Fully tuned amount of users % (VSImax) Windows 7 Windows

20 RECOMMENDATIONS & CONCLUSIONS VMware OSOT is for everyone User Experience vs Tuning Big impact on memory Unlearn: fixed page file / view debug / overcommitting Big impact on Storage CPU Main Bottleneck Test yourself!!!

21 21

22 JOSEPH JABBOUR Manager of End User Computing Willkie Farr & Gallagher LLP

23 GRAPHICS HOW DO I LOOK?

24 WILLKIE FARR & GALLAGHER VDI INFRASTRUCTURE VDI: Citrix XenDesktop Provisioning: Citrix Provisioning Services Hypervisor: ESXi 6.0 Servers: Cisco UCS C240 M4 Graphics Card: NVIDIA GRID K1 Cards Storage: EMC XtremIO Desktop: Citrix Receiver 4.4 with Desktop Lock Remote Access: Citrix NetScaler 11

25 VDI SUCCESS KEY 589: GRAPHICS PERFORMANCE My user s don t use AutoCAD or Photoshop. NVIDIA GRID Pass-through vs. vgpu K series vs. M series Intel Iris Pro Tiered Models User Experience

26 JIM P. NIXON Application Support Manager Seyfarth Shaw LLP

27 RAM CACHE ME

28 SEYFARTH SHAW VDI INFRASTRUCTURE VDI: Citrix XenDesktop Provisioning: Citrix Provisioning Services Hypervisor: XenServer Servers: Cisco UCS B200 M3 Graphics Card: NVIDIA GRID K1 (Testing only on C240) Storage: Whiptail SSD Nimble hybrid Remote Access: Citrix NetScaler SDX (10.5 instance)

29 WHAT IS CACHE IN DEVICE RAM WITH OVERFLOW ON HARD DISK? Write-cache buffer in memory that overflows to disk when full Default is 64 MB but can be changed Is not the same as Cache in device RAM

30 HOW DOES IT WORK? Uses Non-paged pool RAM to map the memory buffer 4 MB vdiskdif.vhdx is created instead of the classic.vdiskcache file Uses 2 MB blocks instead of 4 KB blocks Memory buffer is used first for writes, stale data written to file

31 WHY IS SEYFARTH USING IT? Addresses an issue with Microsoft ASLR and Provisioning Server (CTX139627) Resolves random application crashes due to ALSR issue (App-V, WebEx, etc..) Performance gains as writes always hit memory first

32 GOTCHAS! Larger write blocks mean larger write cache needed for overflow Uses precious memory resources. Plan for more RAM!

33 SIZING GUIDELINES (VIRTUALFELLER.COM)

34 QUESTIONS

35 SURVEY Please rate this session Session #ILTA145