George Crump


Upcoming Events

Cloud Connect
Santa Clara
Feb 13-16, 2012

Cloud Connect brings together the entire cloud eco-system to better understand the transformation we're experiencing and promises to be the defining event of the cloud computing industry. Learn about the latest cloud technologies and platforms from thought leaders in Cloud Connect’s comprehensive conference.

Register Now!

More Events »

Subscribe to Newsletter

  • Keep up with all of the latest news and analysis on the fast-moving IT industry with Network Computing newsletters.
Sign Up

The Truth About Shelf Based SSDs

Shelf based SSDs are SSDs designed to be installed into storage system manufacturers' current drive expansion shelves that they currently use for mechanical hard disk drives. It seems like a good strategy and a quick path to an SSD offering for storage manufacturers. The truth is, however, that either manufacturers or the storage manager need to be aware of the ramifications of loading up a shelf of SSD technology.

Companies like STEC and Pliant Technology offer drive slot compatible SSD drives. In fact, Pliant just announced a high performance, dual ported drive that is at the top end of performance for the category. There is nothing wrong with the technology itself, instead the challenge is going to be with the storage OEMs and how they implement the technology.

These are more than just faster hard drives, they are 15X to 30X faster, depending on the application and your read-to-write ratio. As we outline in our Visual SSD Readiness Guide, determining what applications can take advantage of SSD takes some investigation on your part, but it is not difficult. Knowing the read-to-write ratio is important in determining what SSD technology to use and what kind of performance you can expect. For example, some will provide better performance on mixed read/write workloads than others.

Storage system manufacturers have to break out of the old way of thinking; filling up a shelf with many SSD drives is not like filling it up with mechanical drives. In the mechanical world, the I/O capabilities of the shelf were never an issue. In the SSD world, a half dozen drives may max out the I/O capabilities of the shelf, add more drives, and you won't see any more performance. A full shelf SSD will still outperform a shelf of mechanical drives, but it will be nowhere near what you are paying 15X more for. I think customers are going to want to get all the performance coming to them.

Storage systems manufacturers are going to have to give customers detailed best practices guides. Do they implement half full shelves and build the array vertically up the rack? Can you then mix slower drives in the same shelf for capacity centric applications? Will the dramatic difference in performance cause issues? This is more complicated than when we were mixing SATA and fibre mechanical drives for the first time. Could it be a viable alternative to come out with lower drive slot count but high performance shelves that are only for SSD?

Lastly, what is the impact on performance of the SSD by the array software itself? SSDs may show flaws in storage software design and cause unpredictable performance as you start to take snapshots, replicate or leverage tiered migration with SSD based technology.

It is because of these questions that dedicated appliance solutions like those from Texas Memory or Violin Memory continue to do well. They are not encumbered by having to mix legacy mechanical drive technology or deal with array software overhead.

Shelf based SSDs are not bad, they make a lot of sense. However, more so than any other bandwidth upgrade, 1GBE to 10GBE for example, the additional performance is going to expose previously hidden weaknesses in the environment. The pressure is on the storage manufacturers to address the mechanical legacy of today's storage systems in order to take advantage of what SSD can deliver.

Related Reading


More storage-networking-management Insights



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

Network Computing encourages readers to engage in spirited, healthy debate, including taking us to task. However, Network Computing 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. Network Computing 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.
 

Research and Reports

Hypervisor Derby
August 2011

Network Computing: August 2011

TechWeb Careers