GO HyperScale: Mind-blowing Performance Starting at $128/Desktop
•Download as PPTX, PDF•
1 like•599 views
In the realm of desktop virtualization, storage gets expensive. VERY expensive! With Typical VDI deployments, 40-60% of the total cost per desktop storage and you still don’t get the storage performance of a PC. Atlantis HyperScale not only provides you the necessary hardware to host 600 persistent desktops per appliance at only $128 per desktop, it also equips you with enough all-flash storage to make your desktops perform better than PCs with SSDs!
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to GO HyperScale: Mind-blowing Performance Starting at $128/Desktop
Similar to GO HyperScale: Mind-blowing Performance Starting at $128/Desktop (20)
Recently uploaded
Recently uploaded (20)
GO HyperScale: Mind-blowing Performance Starting at $128/Desktop
- 1. GO HyperScale: Mind Blowing Performance Starting at $128/Desktop June 2015
- 2. 2 Patrick Brennan, Atlantis Computing Sr. Product Marketing Manager – Applications & Platforms Dane Young, Entisys Solutions Citrix Technology Professional (CTP), VMware vExpert, and Virtualization Practice Manager Dennis Geerlings, Login VSI Support Engineer Manager
- 3. Agenda • Solving VDI Challenges with HyperScale • HyperScale VDI Architecture Overview • LoginVSI • Reference Architecture Findings • Wrap-up and Q&A
- 4. 4 Solving VDI Challenges with HyperScale
- 5. © Atlantis Computing Confidential & Proprietary PC vs. VDI: Price and Performance CAPEX $600-$1000 USD CAPEX $1600 USD* 80-150 IOPS/user < 80 IOPS/user IOPS/user (* Gartner Estimate) Traditional PC CPU ~$200 RAM ~$80 Storage ~$60 CPU ~$23 RAM ~$26-80 SAN Storage ~$1000 © Atlantis Computing Confidential & Proprietary
- 6. © Atlantis Computing Confidential & Proprietary Traditional Storage: Too Costly for VDI Storage $495 58% Microsoft VDA $100 12% Broker/Hypervisor $150 18% Server/Network $100 12% Source: Atlantis Computing Cost Calculator COST PER VDI COMPONENT (Persistent) $845 / Desktop!
- 7. © Atlantis Computing Confidential & Proprietary Persistent, Stateless, SBC Models Hypervisor Stateless VDI • Low storage cost • Limited customization Persistent VDI • PC-like environment • High storage cost SBC/XenApp • Lowest cost • Shared sessions/app compatibility Session Session . . . Session Session Session Session . . . Session Session Session Session . . . Session Session Hypervisor User Profile/ APPS/OS Hypervisor OS /App Image OS /App Image OS /App Image OS /App Image OS /App Image APPS OS User ProfileUser Profile/ APPS/OS User Profile/ APPS/OS APPS OS User Profile APPS OS User Profile APPS OS User Profile APPS OS User Profile APPS OS User Profile
- 8. 8 Go HyperScale: Simplify Simplify Your Datacenter Atlantis HyperScale
- 9. 9 Atlantis HyperScale All-Flash Performance Databases: More transactions Virtualization: Faster VMs VDI: Better user experience 50-70% Lower Cost 52% lower cost than hybrid hyper-converged 74% lower cost than traditional storage + compute Modular Scalability Scale-out linearly Scale-out performance and capacity with every appliance Extreme Simplicity Usable storage in less than 60 minutes One number to call for all support
- 10. 10 Your favorite server platform Turnkey 4-node appliance 12TB or 24TB of All-flash storage capacity Available with VMware vSphere or Citrix XenServer Supported by Atlantis (24x7x365 with 4 hour response)
- 11. 11 Scale-Out Modularly Small Building Blocks Linear scale-out performance Predictable economics Pay-as-you-Grow
- 13. © Atlantis Computing Confidential & Proprietary Lowest Cost for VDI SAN + Servers Atlantis HyperScale Cost Per Stateless Desktop $525 $128 (up to 75% less) Cost Per Persistent Desktop $595 $225 (up to 63% less) • Costs include compute, storage and Atlantis licensing where applicable. • Density based on a Knowledge Worker profile as defined by LoginVSI
- 14. 14 HyperScale VDI Architecture Overview
- 15. 15 Atlantis HyperScale Atlantis HyperScale Server Specifications Server Specifications Per Node CX-12 CX-24 Server Compute Dual Intel E5-2680 v3 (2.5GHz - 12C) Hypervisor VMware vSphere 5.5 or Citrix XenServer 6.5 Memory 256GB - 384 GB 384GB - 512 GB Networking 2x 10GbE & 4x 1GbE Storage Local Flash Storage Per Node 3x 400GB SSD 3x 800GB SSD Total All-Flash Effective Capacity (4 Nodes)* 12 TB 24 TB * “All-Flash Effective Capacity” is the capacity available to the application after Atlantis HyperDup data reduction and data protection. This capacity number shown includes data protection to support resiliency with 1 of 4 nodes failing and a 70% data reduction rate. The data reduction rate will vary based on workload, which could result in an effective capacity that is higher or lower than the number shown.
- 16. 16 HyperScale Architecture HypervisorHypervisorHypervisor Storage 3 x 400GB SSD Compute & Network 2 x Intel E5-2680 v3 384 GB RAM ESXi 5.5 U2 2 x 10GbE, 2 x 1GbE Hypervisor Volume VM All-Flash Volume HA Enabled NFS 73GB RAM Volume VM All-Flash Volume HA Enabled NFS 73GB RAM Volume VM (HA) All-Flash Volume HA Enabled NFS 73GB RAM Volume VM All-Flash Volume HA Enabled NFS 73GB RAM Service VM HA Enabled 40GB RAM Total VDI Desktops 2vCPU 2 GB RAM 1Gb NIC 40GB Disk
- 17. Environment Details Software Components Component Description VDI Broker and Client Citrix XenDesktop 7.6 & StoreFront 2.6 Hypervisor & vCenter VMware ESXi 5.5 U2 Atlantis HyperScale Atlantis USX 2.2 Benchmarking/Load Gen. Login VSI 4.1.3 VDI VM Configuration Component Quantity Description Operating System X Windows 7 SP1 – 64-bit vCPU 2 2 virtual sockets, 1 core per socket Networking 1 1GB – Management Network RAM 2GB Disk 40GB VM disk stored on the Atlantis HyperScale Volumes NO OPTIMIZATIONS PERFORMED!
- 18. Testing Methodology • Scalability Test • Determine overall HyperScale VDI “real world” scalability • HA Test • Observe behavior in the event of a node failover and evaluate performance • Iometer • Evaluate IOPS • PassMark • Compare against other SSDs, etc.
- 19. 19 LoginVSI
- 20. LoginVSI
- 21. LoginVSI – VSI Max & VSI Base • What is VSI Max and VSI Base? • What do they tell us? • How are they measured? VSIbase Performance 0 - 799 Very Good 800 - 1299 Good 1300 - 1999 Reasonable 2000 - 9999 Bad
- 23. 23 Scalability Test – VSIMax & CPU Login VSI Test – VSI Max & CPU Metric Measured VSI Max 608 (Max not met, spare capacity) CPU Utilization (Average) 53% CPU Utilization (Peak) 92%
- 24. 24 Scalability Test – Memory Active Login VSI Test – Memory Active Metric Measured Average Memory Consumption (Active) 147GB Peak Memory Consumption (Active) 171GB Average Memory Consumption (Consumed) 350GB
- 25. 25 Scalability Test – Disk Latency Login VSI Test – Disk Latency Metric Measured Disk Latency (Average) 0.017ms Disk Latency (Peak) 1ms
- 26. 26 © Atlantis Computing Confidential & Proprietary HA Test – VSIMax & CPU Login VSI HA Test –CPU Metric Measured Login VSI Max 490 (Max not met, spare capacity) CPU Utilization (Average) 52% CPU Utilization (Peak) 98%
- 27. 27 © Atlantis Computing Confidential & Proprietary HA Test - Memory Login VSI HA Test - Memory Metric Measured Max Memory Consumption (Active) 187GB Average Memory Consumption (Active) 108GB
- 28. 28 © Atlantis Computing Confidential & Proprietary HA Test – Disk Latency Login VSI HA Test – Disk Latency Metric Measured Average Disk Latency 0.218ms Peak Disk Latency 9ms
- 29. 29 Iometer Iometer Metric Measured Volume IOPS (80% Write, 80% Random) 57,238.52 Total IOPS (80% Write, 80% Random) 171,715.56
- 30. 30 PassMark Benchmark PassMark Benchmark Test Metric Measured PassMark Disk Score 5227
- 31. 31 Results Summary Phase 2 Test Results Test Results Iometer 171,715 Passmark Disk Score 5,227 Deduplication Rate 99% Physical Storage Consumed for 600 VMs 238GB Phase 1 Test Results (Per Node Average) Test VSIMax CPU Utilization Active Memory Disk Latency Login VSI - Login Test 600* 53% 147GB 0.017ms Login VSI - HA Test 500* 52% 108GB 0.218ms *Additional capacity available for a higher VSI Max score
- 32. GO HyperScale! • Why HyperScale? Cost: Starting at $128 desktop Simplicity: Easy to deploy Performance: Blazing IOPS, faster than SSD! Scalable: Modular, simple, and easy to manage! • For more info & RA visit: http://www.atlantiscomputing.com/hyperscale • Contact our strategic partners like Entisys for more details!
- 33. 33 Poll
- 34. 34 Q&A
Editor's Notes
- Let’s get back to basics on how VDI is built and why Atlantis is so focused on this workload. Performance on PCs and laptops have ceased to be an issue for years. CPUs run faster than most people need and the addition of flash or hybrid drives has had a significant impact on user experience. Graphics quality continue to improve and even integrated graphics chips deliver very good quality graphics for general use. Cost continues to decrease as the cost of even the most feature-rich PC or laptop rarely exceeds $1000 and tends to average out around $600-700. As a key indicator of PC performance, an average PC can generate 80-150 IOPS or more depending on whether there is a flash-based or flash-enhanced disk drive involved. Transition … As we move to VDI, all of these local components get shifted to the Data Center. RAM, CPU, and graphics are now housed in a server blade, meted out to users via virtual machines. The storage component has generally migrated to the SAN array which is interconnected to the server via a high speed networking fabric. For all kinds of reasons, centralization is a great benefit but it comes at a cost. Even though shared with multiple users, the provision of desktops on Data Center-quality servers and storage is expensive. In fact most VDI deployments are more expensive per user than the PC it is replacing. Up to twice as expensive in fact! When we start sharing expensive server CPU, RAM, and Graphics resources, there can be some degradation in performance depending on how the environment is architected. But, by far, the greatest impact to user experience is the IO barrier put in front of the virtual desktop to accessing disk resources, especially where OS and application componentry comes in. The desktop OS is used to having free access to disk and is not aware that it has been virtualized. So all of the overhead associated with physical hard drive maintenance and access continues to occur, now over the storage area network on disks that have been designed for read vs write performance. In fact a desktop can consist of 70-80% writes. Since the SAN is busy with many other read and write requests, the desktop VM must wait its turn to read or write data. This wait time is compounded by much of the now-useless physical disk management routines which the SAN must take time to deal with. So as we discussed, IOPS is a key limiting factor to virtual desktop user experience. In a typical old school VDI deployment, IOPS have been throttled to 80 or less to keep overall costs at anywhere near the $1600 per desktop instance that Gartner suggests. 80 IOPS will generally provide your users with overall poorer user experience than their old physical PC, driving a stake into the heart of user acceptance of VDI. (And costing the company more to boot!) So what is by far the biggest contributor to high cost and low performance of VDI? Centralized storage. This remains the Achilles Heel to VDI !
- Gartner has a birds eye view on VDI projects across 100s of companies., Storage represents almost 60% of the entire VDI CAPEX adding up to an average of $1000 per user. By itself, that’s more than buying all but the fanciest laptop. Gartner also notes in their report that it is important to balance cost with user experience. But we all know by now that throwing money at storage isn’t necessarily going to drive good user experience. (Transition to next slide) Gartner Report: “The No. 1 challenge associated with any SHVD [VDI] project, is the lack of storage planning resulting in higher-than-expected storage costs.” “Today, storage represents 40% to 60% of the SHVD budget and, in many cases, is a barrier to entry.” “Cost should be carefully balanced with user experience.”
- The way you deploy VDI or XenApp also has a significant impact on the cost and performance of the solution. Persistent VDI offers the least difficult migration path since existing OS images are simply copied onto the storage array and deployed on the virtual desktops one by one. While simple, this magnifies the cost of the overall solution by requiring large swaths of SAN storage for each and every desktop user. And of course each user will consume IOPS writing and reading the SAN with each app or OS interaction. MCS and Linked Clone image management may ease the initial storage capacity issues but the difference disks per user tend to grow over time, expanding storage consumption. And neither approach offers significant benefits to performance. Stateless VDI leverages a single OS image which is deployed to each VM each time the VM is powered on. This reduces significantly the amount of storage required for VDI but creates challenges to customization since user preferences must be maintained separately from the image and installed apps are generally hard to support. What doesn’t change is the IO required to the storage array since the same number of users are accessing the SAN to access the single image. XenApp provides a shared desktop as part of the Windows Server OS. Again, only a small SAN footprint is required but customization is difficult, even more so than with Stateless VDI. The biggest bottleneck is now the write cache of the image management solution (PVS). The SAN must again support large amounts of IO as a large number of users access their shared desktops. So while each methodology has different ways of handling desktop OS images and providing user customization, they all share the challenge of providing a reasonable level of IO to the storage array.
- HyperDup data services enable Atlantis to deliver much more storage capacity at a much higher level of performance than any other solution in the industry, reducing our cost up to 82% for VDI and up to 67% for server workloads. CX-12 with 384GB RAM: $79087 excluding support 608 Stateless users 350 Persistent users
- VMware 5.5 U2, vCenter 5.5 – 1 Cluster XenDesktop Launchers on another host+vCenter
- 384GB MAX
- Scalability Test: 171GB Peak
- Scalability Test - 0.017ms Latency
- -Backup Questions: How did you provision the VMs? All various methods of provisioning from XD are supported however we used our own method. We have an agent that you can install into the VM. Then we use scripts on the USX volumes that takes a VM template, injects the computer account and domain information. When the VM boots up the first time, it automatically changes the name, adds itself to the domain in the respective OU and reboots ready to go. How was the networking setup? We used 2 NICs for the domain/management network and the 2 10GB NICs for storage. We didn’t measure traffic but it was rather minimal since we’re not using anything like PVS. Which HyperScale appliance was used for this RA – Lenovo As you add more HyperScale appliances can you manage it with the same console? Yes as you add more appliances, you would use the same admin console to manage all of the appliances you bring into the environment rather than a separate console for each appliance.