Commentary

George Crump
 

The Case For Specialized Hardware

As we described in the last few entries, adding storage software to standard servers or even to virtual servers is making more sense for a variety of data centers because of the increased performance capabilities of the Intel processor family. Despite this there may still be times in certain environments where there is a need for specialized storage hardware.

As we described in the last few entries, adding storage software to standard servers or even to virtual servers is making more sense for a variety of data centers because of the increased performance capabilities of the Intel processor family. Despite this there may still be times in certain environments where there is a need for specialized storage hardware.Large cloud compute environments and large scale virtual environments for example may put so much strain on the storage infrastructure that certain tasks may be better off being offloaded to a specialized piece of hardware. Along with virtual environments, what we are asking the storage systems to do today is more significant than in the past. Capabilities like thin provisioning, back-end disk virtualization, snapshots, dual parity raid, local and remote replication all demand more of the storage compute resources.

As these capabilities mature and are understood, more will be asked of them. In the past if you used snapshots for example, it was enough to have one or two snapshots and use those snapshots just to recover a corrupted volume. Now it is not uncommon for snapshots of a volume to number in the high double digits, and for you to expect to not only recover from that volume but to also mount it in a read/write fashion so you can leverage it for testing. This consumes storage compute resources.


More Storage Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Another example that is maturing right in front of us is thin provisioning. As we outline in Thin Provisioning Basics, thin provisioning is the capability to provision storage in advance but only consume disk space when it is physically needed. However with increased use, we are learning that is not enough. Thin provisioning systems have to become more aware of the data they store. They need to differentiate between what is actual data and what is data that has been marked for deletion. Doing so allows for the migration of fat volumes into a thin provisioned system and the maintaining of thin volumes as they are used and data is deleted from them. Again calculating and managing all of this provisioning consumes storage compute resources.

The combination of large virtual infrastructures with these advanced capabilities means that more is being asked from the storage infrastructure. Now more than ever you may hit the upper edge of performance of a storage system long before you finish populating it with drives. Certainly the Intel wave may catch up with the performance demand, but realize that these capabilities are just the beginning. On the plate next is embedded data migration between storage tiers, deduplication, compression and of course being able to maintain performance across more than a few SSD drives inserted into the storage system. In addition there are probably a host of other capabilities that we are yet unaware of.

To maintain performance in these large scale environments there is going to be an increased demand for clustered storage and specialized hardware. These demands for data services are going to require a scale out architecture with potentially specialized engines for off-loading some of these tasks. Doing so will allow storage systems to maintain maximum performance and deliver full capacity.

Track us on Twitter: http://twitter.com/storageswiss

Subscribe to our RSS feed.

George Crump is lead analyst of Storage Switzerland, an IT analyst firm focused on the storage and virtualization segments. Find Storage Switzerland's disclosure statement here.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links