Solving the I/O bottleneck issue: Most options mask rather than solve

Why does virtualization cause the I/O bottleneck problem?

    Requires Free Membership to View

You're basically doing an emulation within VMware and within a hardware controller for storage. That emulation -- virtualization of a controller -- stands between your applications and the use of the actual physical hardware underneath, and that creates an I/O bottleneck. So you have this emulation of a hardware controller sending and receiving I/O from the storage complex and it gets in the way.

Unfortunately, a lot of people are being conned right now -- and I use the word con deliberately -- into believing that if you throw flash or some sort of high-speed storage at the problem it's going to alleviate it. That's kind of a brute-force attack. Your I/O bottleneck is rooted in the virtualization software stack. It's not a problem with I/O itself or the configuration with the networks; it's none of those things. It’s not a question of the speeds and feeds of the equipment down below. You can brute force it, make it appear like it's working faster, by writing all your outbound writes to memory first. Then the memory signals, "OK, we got it" and you go to your next operation. Then it takes its own time in writing the data to the back-end software. You can do that; that's caching, and it's been done for years.

It's also known as spoofing. It's the way NetApp Filer -- for those people familiar with network-attached storage -- works. NetApp's back-end WAFL [Write Anywhere File Layout] system plus its RAID system aren't the world's greatest performers. So what you do is you cache in front of it for what they call Flash Cache cards, which are memory, and you cache all the incoming traffic in the memory once the write has been made and let the write occur later on, as the system catches up. That's a way to spoof the I/O bottleneck issue, but it doesn't resolve the problem. And it's going to get worse; the more workloads you stack up inside a server, the worse that logjam is going to get.

This was first published in March 2013

There are Comments. Add yours.

TIP: Want to include a code block in your comment? Use <pre> or <code> tags around the desired text. Ex: <code>insert code</code>

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
Sort by: OldestNewest

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to: