Nothing could be further from the truth.

I believe that this stems from the fact that the industry is stuck on using the HDD metric of $/GB and single drive cost as the primary measures of the cost. As I wrote in a previous post, “Storage managers getting wise to prevailing SSD limitations”, looking at historical or single drive cost metrics doesn’t accurately measure solution-level costs. So let’s try this again.

Yes, individual enterprise-class solid state drives (Enterprise Flash Drives) cost more than individual enterprise hard drives. So having stated this fact, let’s also be sure to state the fact that EFDs offer tremendous performance boosts (>100X), and can replace many 15K RPM HDDs. Budget constraints require that enterprises and data centers focus on maximizing both performance and efficiency, so transaction cost ($/IOPS) is also a key metric.

The goal is to provide a storage solution that optimizes for both $/GB and $/IOPS.

Let’s look at a typical data warehousing application from the TPC-C benchmarks (http://www.tpc.org/tpcc/results/tpcc_perf_results.asp). The storage solution must provide 640,000 transactions/minute (320,000 IOPS) for 18 TB of data. With a typical all-HDD solution, this requires:

• 1000 15K 2.5-inch HDDs (short stroked to 18GB)
• 40 rack mounted shelves
• 8000 watts to operate and (an additional) 8000 watts to cool
• Price tag = $ 450,000

Now, let’s look at how a ‘hybrid’ approach combining EFDs and existing HDDs can not only provide a lower transaction cost, but also a lower cost/GB and a lower total cost. This hybrid solution would be configured as outlined below:

Not only does the hybrid approach offer a much lower $/GB and $/IOP (and requires 34 fewer shelves), but the total cost is one-half that of the HDD-only configuration.

Did you catch that?  One-half the total cost.

At the end of the day, the numbers don’t lie. The value proposition of EFDs is simple, it provides ‘more for less’ – more performance for less cost, less power and floor space, and more reliability. And, EFDs can be managed with existing software.

What will IT managers do with all the savings?

Amyl Ahola

This ‘revelation’ appeared in a SearchStorage.com article by Beth Pariseau, “Storage admins mull SSDs at SNW.”  The article quotes multiple storage administrators who all basically believe in the benefits of SSD, but stop short of saying that the technology is ready for prime time.

Here are their top concerns: predictable performance, data integrity, the lack of consistent, industry-accepted SSD benchmarks, and cost.

Let’s quickly look at each of these:

1. Predictable performance – I covered this recently in my “’Predictable performance’ for changing business dynamics” post. This area has traditionally been a challenge for SSDs in enterprise applications because workloads are random and indeterminate. Predictability requires consistent performance, independent of whether reading or writing data, because enterprise applications typically vary the read-to-write ratio between 60/40 and 90/10. Enterprise SSDs should be able to maintain performance across this range.
2. Data integrity – I couldn’t agree more that data integrity features are critical if flash technology is to perform at enterprise levels, and the Data Integrity Field (DIF) standard is an important step in this direction. Yet, today so few storage devices support the DIF standard. Pliant began mapping toward the DIF standard early on, recognizing how important it was for enterprise-class storage systems.
3. Standardized benchmarks – In my post, “SSD jargon and the need for standards,” I listed a number of pivotal questions that must be addressed if the industry is ever to develop more accurate, relevant – and yes, consistent – SSD benchmarks. These include making sure that real performance is measured and that product lifecycle benchmarks are based on true, 100% duty cycle operation. If product life metrics are contingent on usage limitations – e.g., based on a maximum number of writes or writes per day due to limited error management capability – then the benchmarks are virtually useless.
4. Cost – Transaction cost (IOPS per $) is the key SSD metric to consider, not the old HDD industry metric of $/GB. This metric is an irrelevant measure of SSD value as a performance solution, and we expect EFDs (Enterprise Flash Drives) to complement high capacity HDDs to optimize for both $/IOP and $/GB.

With most existing vendors either falling short on a number of these points, or masking the limitations of their devices behind carefully crafted marketing spin, it’s no wonder why some storage admins are still skeptical.

This is why I continue to extol the values of EFDs, a new class of solid state storage devices designed with key enterprise considerations in mind. By definition, EFDs are designed to address all of the above issues.

And, as we prepare to announce availability of our first products shortly, my hope is that our approach will help turn the heads and change the minds of the remaining nay-sayers in the industry.

Amyl Ahola

The list of SSD jargon Kerekes cites in the article includes: dynamic leveling, active leveling, static leveling, BCH codes, Reed Solomon codes, write endurance, write amplification, write attenuation, garbage collection, read patrol, wear leveling, read disturb, and program disturb.

Look at the last two.  These are rarely discussed but are among the most important issues to those who care about losing data.  An earlier STORAGEsearch.com article asks the question, “Can you trust your flash SSD specs & Benchmarks?”  The answer can only be ‘of course not!’  At least not until there is some semblance of standardization.  This is especially true when considering using SSDs to meet the performance and reliability demands of enterprise applications.

With this in mind, some questions that should be asked (and answered) about SSD performance and reliability specs and benchmarks are:

1.    What is the real performance?

A simple question but rarely, if ever, addressed in the specifications.  Typical environments are random, 60%-70% read, and 4K/8K blocks.  Not small blocks (512b) to show high IOPs, or large blocks to show high bandwidth.

2.    Is the performance deterministic?

The writing process for flash is inherently slower than reading.  Does the performance drop substantially as a function of the read/write mix or does it stay relatively constant as needed to maintain consistent response times?  Is the performance dependent upon the use of cache (and the associated power loss and recovery issues of volatile cache memory)?

3.    Is the performance sustainable?

What does ‘sustainable’ mean? It is not unusual for performance to degrade as more and more of the device gets written to…it may take minutes or hours, but degradation of 50% or more may occur.

4.    What is the capacity available to the user?

Another simple question, but all SSDs contain more flash than that available for end user data. For example, the additional (or over-provisioned) flash may be used to optimize write performance, provide for spare blocks, CRC codes, ECC codes, and meta data.  Does the stated capacity net this all out?

5.    Are there duty cycle or other limitations on usage in order to achieve/maintain the specifications?

Does the architecture provide for 100% duty cycle, or is the product life contingent on a maximum number of writes or writes per day due to limited error management capability.

Is it assumed there will be ‘adequate’ idle time (what’s that in the enterprise?) to perform the necessary flash management activities?

6.    Are the error management and ECC algorithms powerful enough to correct read disturb and program disturb errors without resulting in excessive rates of uncorrectable errors and/or losing capacity due to bad block mapping?

Error correction approaches which utilize limited ECC to correct random bit failures may not have sufficient correction capability for read/program disturb errors. Correction capabilities may appear adequate but be based on codes, such as the Reed Solomon code, which is great for hard drives but not really applicable to flash failure modes. The lack of idle time for background flash management makes this problematic for many / most SSD architectures.

Kerekes sums it up well: “Better user education about SSDs is a critical factor for the industry to sustain its growth. Design trade offs in products go far deeper than the choice of memory and interface. Being aware that there are other parameters which SSD vendors have implemented well, badly (or not at all) can be the difference between a satisfactory or disillusionary experience.”

What do you think?

Amyl Ahola

So, I think a description and definition is in order. 

In the world of disk drives, enterprise-class products are distinguished from desktop and laptop products by their ability to provide superior performance and reliability.  This means that they are expected to perform flawlessly in mission critical environments.  This same requirement also holds true for enterprise SSD devices.  However, just like lower-end disk drives, SSDs designed for laptops and desktops simply can’t pass muster when expected to provide the performance and reliability required in a mission-critical enterprise environment.  There are a number of existing SSD products marketed for the enterprise, many of which are nothing more than re-packaged consumer grade (laptop) SSD technology.  In fact, many of the so-called “enterprise SSD” drives actually underperform HDDs in laptop applications…hardly what I would call enterprise class. 

Therefore, a true EFD must provide high levels of performance and reliability for flawless operation in mission critical, I/O-intensive environments.  Given the growing power and space concerns of today’s large enterprise environments, reduced energy consumption is becoming an equally important criterion for any new class of primary storage devices.  An EFD’s superior performance, energy efficiency and improved reliability allow data centers to substantially grow capacity and performance in existing installations while reducing energy needs and TCO.

Given these requirements, an Enterprise Flash Drive should, at a minimum, provide the following:

1. Superior I/O Performance – Adequate I/O performance levels to prevent bottlenecks, even during peak activity periods (generally 3-5 times greater than typical activity periods), without requiring extra hardware (i.e., cache)  while providing ample scalability for growth.  At a minimum, an EFD should deliver at least 100,000 random IOPS or more and be able to sustain this rate for typical block sizes (4K bytes or more). 
2. Exceptional Reliability – EFDs need to deliver significantly lower failure rates than disk drives, given the inherent benefit of solid state technology (no moving parts).  Performance and reliability must be predictable and sustainable at 100 percent duty cycles (24/7/365) without cycle-stealing maintenance or “housekeeping” actions.  Lifetime should exceed five years without performance or capacity degradation.  Robust reliability monitoring and reporting capabilities are essential.
3. Energy Efficiency – EFDs should meet new standards for green data center excellence of greater than 20,000 IOPS per Watt, with activity-based power management to limit energy consumption when the device is less than 100 percent utilized.
4. Cost Efficiency – Transaction costs ($/IOPS) must be substantially reduced from that of an HDD (<10%).  And, it goes without saying that an EFD must be form factor and interface compatible with HDDs (while providing similar storage capacities).

While these requirements are very demanding, I believe they only begin to define the needs and ability of solid state technology to transform future system and storage architectures.  In my opinion, the vast majority of today’s SSD products are already falling short of the true needs. 

Interested to hear what you think…

Amyl Ahola

Enterprise storage applications are demanding, and it is essential that reliability specifications are met at a 100-percent duty cycle operation on a 24/7/365 basis.  Those in the industry know that true enterprise-class disk drives are required for this environment, and that disk drives designed for low cost and low duty cycle laptop/desktop applications literally fall apart when employed in an enterprise application.  Likewise, SSDs designed for laptop/desktop applications also do not even come close to meeting the need.  So, for Enterprise Flash Drives to be accepted in the enterprise they must meet or exceed enterprise class HDD reliability. This is not a trivial task. 

The primary enterprise reliability specifications take the form of MTBF (or more meaningfully: annualized failure rate) and non-recoverable error rates (lost data).  Flash technology has three primary failure phenomenon that have a significant impact on reliability:

• Write Endurance – the limit on how many times a cell can be written/erased before it becomes damaged
• Write/Program Disturb –  writing to a given page in a Flash chip can alter bit(s) in a page that is not being written (does not damage the cell); this is sometimes referred to as “bit flip”
• Read Disturb – similar to Write Disturb, reading a page in a Flash chip can alter bit(s) in a page not being read (does not damage the cell)

A further complication is that these failure modes are not independent.  For example, the read disturb error rate is related to the number of writes or erases so that write endurance and read disturbs (and write disturbs) must be holistically considered.  It is obvious that they all contribute to non-recoverable errors, but perhaps not as obvious that they contribute to MTBF as well.  MTBF is a measurement of performance to specification, not just to some catastrophic event, as is typical with a disk drive.  This includes meeting performance and capacity specifications.

A common approach used in typical SSDs to deal with write endurance is to incorporate a wear-leveling algorithm to distribute writes across blocks within the chip(s), together with error correction (ECC), so that any damaged cells can be corrected when read.  This same ECC can then be applied for all reads to detect and correct altered bits (‘bit flips’) independently of how they became defective, i.e., write endurance, read disturb, or write disturb.  If the number of defective bits exceeds the ECC threshold, the sector(s) being read would then have to be marked as defective (non-recoverable error) and made unavailable to the system.  Depending on the amount of spare Flash capacity, at some point the resulting system capacity may well drop below the specification.

As an example, a well-known supplier of SSDs advertises an ECC that corrects up to 8 bytes in 1024 bytes, while another supplier advertises 6 bytes in 528 bytes.  At the same time, both talk about program erase/write cycles well in excess of 1 million.  However, tests show that both ECC levels would frequently result in non-recoverable errors after as few as 200,000 write/erase cycles.  These error rates result in SSD reliability falling far short of disk drive reliability in terms of non-recoverable error rate.  At the same time, overall capacity begins to erode and eventually falls below the device specification, resulting in an MTBF failure. 

And, that’s not all.  There is also a significant performance impact resulting from the management of these high error rates (It drops dramatically!).

The primary point is that enterprise-level reliability, whether it’s MTBF or non-recoverable error rate, can not be addressed with just traditional ECC.  Other techniques must be employed in addition to ECC to manage errors.  In addition, these additional techniques cannot be allowed to significantly impact performance (IOPs or bandwidth).

Sounds like a daunting task…or is it??  Stay tuned.

 Amyl Ahola