Evaluating Storage for VDI Projects
•
2 likes•889 views
Storage is the item most often responsible for performance success or failures, and also has the largest impact on total costs. Achieving good cost - performance levels requires a storage architecture optimized for VDI. The issues relating to storage can be categorized into three areas: storage capacity, storage performance requirements, and administrative changes. This presentation provides a brief overview on what you should consider when evaluating storage for VDI.
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Similar to Evaluating Storage for VDI Projects
Similar to Evaluating Storage for VDI Projects (20)
Recently uploaded
Recently uploaded (20)
Evaluating Storage for VDI Projects
- 1. Evaluating Storage for VDI Projects
- 2. Bridging VDI vs. Storage Speak 2 Storage Speak TB $/GB IOPS MB/sec VDI Speak Boot Times $/Desktop Virus Scanning Usage Model
- 3. Capacity Implications from Provisioning Technique 3 Fully Provisioned Static Allocation VDI Cloning Linked Clones 3rd Party Clones MokaFive, Uni desk, Wanova, etc. Storage Clones Writeable Snapshopts Thin Provisioning High Low Low Low Compression Moderate Low Low None De-Duplication High Low Low None Storage Clones High None None N/A
- 4. Performance Implications from VDI Usage 4 Task Automation 10-20 IOPS Typical Office 20-30 IOPS Knowledge Worker 50-60 IOPS
- 5. VDI I/O States 5 Boot and Login Storms Steady State Virus Scanning
- 6. Performance Impact of VDI Operations 6 VDI Function I/O Impact Frequency Provision High Low Clone High Moderate Boot Moderate High Login Moderate High VDI Desktop Use Low High Virus Scan Moderate Moderate Refresh (re-clone) High Moderate Patch Tuesdays High Low
- 7. Unique VDI I/O Profile 7 Boot and Login Storm Steady State Work OS/App Scans and Patches
- 8. More Desktops More Disk More Pain • VDI’s contain a lot of redundant data – OS and end-user applications. – Capacity for One VDI - @15GB, but for 1000 VDI’s - @15TB. A lot of storage for desktops! • The Performance requirements for one VDI are low, but a 1000 VDI’s places significant challenges on the storage subsystem – 1000 VDI’s would require 250 disks. More capacity than is needed. • Still need to provision additional storage related services such as NAS. More islands of storage to purchase and manage 8
- 9. Tegile Breaks the Cycle 9 Stop the linear desktop:spindle correlation
- 10. Tegile – Unified Flash-Driven Storage iSCSI & FC SAN NFS & CIFS NAS for OS, Apps and User Data Accelerated in-line de-duplication & compression for $/desktop reduction Active-active clustered high availability design ensures user uptime Application profiles for different usage models LESS CAPACITY REQUIRED* 75% MORE IOPS* 7X * Compared to legacy mid-range arrays 10
- 11. Tegile Capacity Reduction CompressionDe-DuplicationThin Provisioning Tegile customers purchase 75% less capacity Data is then Compressed OS APP VMDK OS APP VMDK OS APP VMDK OS APP VMDK OS APP VMDK Volumes are Provisioned Thin Redundant data is De-duplicated OS APP VMDK OS APP VMDK OS APP VMDK OS APP VMDK OS APP VMDK 11
- 12. Tegile Performance Maximization SSD Cache Meta Data Acceleration Memory Footprint Tegile arrays run 7X Faster Cache is extended to SSD pool and meta data is processed in SSD Meta Data Accelerated Storage optimizes caching, de-dupe, RAID other functions Hottest data is cached in large DRAM memory pool 12
- 13. Tegile – Unified Flash-Driven Storage 13 Hardware Features Cache – High speed SSD and RAM Capacity – SAS Hard Drives Scalable – 12-106TB physical capacity Up to 60-530 TB effective capacity HA – Active-active controllers Software Features Unified NAS + SAN – Multi-protocol Simple, app-aware provisioning • Virtual servers, desktops (VDI) • Database, File Services & Backup Data protection • Local snapshots & Remote replication • Sophisticated RAID levels • Advanced Reporting
- 14. The Tegile Effect Versus Traditional Storage 14 Traditional Storage Tegile Arrays Tegile Advantage IOPS 75,000 75,000 = Effective TB 112 105 = Rack Units 115 3 97% LESS WATTS 8437 840 90% LESS US List Price $475,000 $100,000 79% LESS
- 15. Tegile Benefits in Virtualized Environments Pine River Capital Active-active controllers delivering 180,000 IOPS 6X the speed of EMC CX at 15% of the price ipHouse Migrated service provider storage platform 3X the speed of incumbents with 60% reduction in capacity Implemented VDI and consolidated file sharing 7X the IOPS of legacy storage with 70% reduction in VDI capacity requirements Washington & Lee University 15
- 16. For more information on Tegile Storage Solutions for VDI http://goo.gl/SuaRW3
Editor's Notes
- The scaling metric is the most important factor as it has a significant impact on cost. It is directlydependent upon the how each desktop is provisioned. There are four choices for provisioningVDI which include:Static allocation for each desktop (also known as Fully Provisioned)Shared allocation for desktop OSo Clones using VDI software (such as Linked Clones)o Clones using Third Party software (MokaFive, Unidesk, Wanova, etc.)o Clones using storage system technologies (such as writeable clones)The architecture chosen has a significant impact on the entire VDI solution including capacity,performance and administration. The benefit of storage capacity features varies with eachmethod of VDI cloning as follows:
- There are a number of use case scenarios common with desktops and VDI. Provided below arethree common scenarios that outline how users interact with their desktops, applications andaccess to file data. These different scenarios can have a major effect on what is required toimplement VDI.Task Automation: The user at a virtual desktop is often a telephone sales or a customer servicerepresentative. Their application use is limited to a small set of applications. There may behundreds or even thousands of these users utilizing a CRM and other applications. This use casetypically involves little or no access to user specific file data.Typical Office: Users are running a standardized set of applications, including typicalproductivity applications as a web browser, a word processor and a spreadsheet. All users areprovided the same applications, which they cannot modify, but they each have different data (e.g.word and spreadsheet documents) that they create, edit and want to save.Knowledge Worker: These users may be designers, engineers or heavily customized officeworkers. Each user has their own desktop environment, including preferences for applications,different from other users, with each managing and maintaining a large set of documents andother file data. I/O intensive operations such as media players, compilers and other applicationsmay be used which impact the environment.This webinar will explore how these different scenarios can have a major effect on the storagesystem requirements. These three scenarios are merely illustrative. There are, of course, otherscenarios, each with their own particular usage patterns. A given implementation could be anycombination of these examples, or other possibilities.