Infinite I/O

How Infinio can save the VDI user experience

Posted by Sheryl Koenigsberg on Jun 12, 2014

Last week we announced that Scott Davis has joined us as our CTO. Scott’s background as the former CTO of VMware’s storage and end-user computing divisions gives him a unique insider perspective on virtualization and VDI. Our Director of Product Marketing, Sheryl Koenigsberg, sat down to speak with Scott.

I’m very happy to have Scott Davis join us here at Infinio. I had a chance to talk with him earlier this week about why he came to Infinio and why he thinks Infinio will be a great solution for VDI environments.

sheryl-and-scott-davis

SK: Welcome to Infinio, Scott. You have this great background on the virtual desktop industry - do you have any insight as to why nearly half of our customers are using Infinio in a VDI environment?

SD: User experience is really crucial to successful VDI deployments. There can be a lot of complexity in delivering the right performance and latency to virtual desktops, and organizations are looking for ways to meet their users’ requirements. The optimizations built into storage arrays have not been very effective in virtualization environments because of the “I/O blender” effect — many VMs issuing I/Os through the hypervisor and thwarting locality optimizations performed by individual guest operating systems.

SK: OK, so what’s different about the performance characteristics of a VDI deployment?

SD: Well, to start, there is a higher consolidation rate for VDI, so this density complicates things.  Not only can the IOPS requirement be high, but they also can be very unpredictable, since it’s all based on what the users are doing on their individual desktops.

And remember, VDI performance isn’t really measured in transactions or throughput, it’s measured in how responsive the desktop is for the user. Without the right latency, it doesn’t matter what kind of IOPS you can drive on the backend storage. If the users don’t think the desktop responsiveness is acceptable, it’s not.

SK: And as a user, I want performance that’s at least as good as my physical laptop was.

SD: Right. But on the economic side, it’s a different story. Organizations go into VDI projects for the manageability, accessibility, and security of the solution. But at the end of the day they are also looking for a way to get these benefits while still keeping the cost per desktop below that of a physical desktop. That’s hard to do and still deliver adequate performance to large numbers of users. Many times, VDI deployments behave fine during the proof-of-concept, but have inadequate performance in production.

But to your earlier question, that’s one of the reasons I think customers are seeking out Infinio in these projects. Infinio can help drive down the cost of what is often the most expensive part of a VDI deployment: the storage. Infinio is also the easiest way to remediate a stalled deployment that was undersized.

SK: One thing I’ve never understood is why there are so many more writes than reads in these environments. I’ve heard numbers as high as 80% writes. What’s going on architecturally that makes this the case?

SD: There are a few things to know here. First, it depends where you are measuring these numbers. In Windows desktops, the NT buffer cache satisfies repeated reads from memory. So there are a lot of reads to commonly accessed files that live in the OS cache and rarely see back-end storage. Similarly, writes aren’t all sent to back-end storage immediately either — think about how you can lose a Word file if you haven’t hit “Save.” This skews the read/write ratio from each VM as measured at the array.

SK: OK, so what you’re saying is that that 80/20 writes/reads number might be what the back-end storage sees, but it doesn’t reflect what the desktop is actually doing.

SD: Correct. With high consolidation ratios, these considerations are multiplied for each guest VM. Also, RAID technology can turn a single write into mulitple writes to different drives for availability.

The other thing at play is that during peak times, those ratios aren’t actually relevant at all. When an array gets backed up and can’t handle the load, all I/Os get backed up. And it’s those peaks that can really bring storage to its knees. Think boot storms, antivirus scans, or updates; all those time-oriented activities.... You can see 10x spikes in I/O at those times. Which is why you need to make sure to have storage that is sized for those peaks loads, or something that can handle them.

SK: ...like Infinio?

SD: Like Infinio. And reads are typically more important for the critical user responsiveness metric. So if we go back to the point about what gets measured in a VDI environment, ultimately it’s how responsive the users perceive the desktops as being.

SK: One more question for you — This conversation has been mostly about why you think customers are choosing Infinio for VDI. But why did you choose Infinio?

SD: Well, it wasn’t to join a read-cache company! I think Infinio has great core technology that’s been well-deployed into server-side caching today. Content-based address is a uniquely transparent and non-disruptive form of storage address virtualization. Over the long term, Infinio has the potential to use this technology to provide other services that are transparent and non-disruptive to deploy. I’m here to help build that vision.

Topics: About Us, Talking Tech