News

11/21/2008
11:45 AM
George Crump
George Crump
Commentary
50%
50%

SSD Can Mean Hard Cost Savings

In our last entry we talked about the time savings and potential increase in productivity and revenue that deploying SSD can enable. This entry we will focus on the hard cost savings associated with SSD. In the right situation, SSD can actually be less expensive than mechanical drives.

In our last entry we talked about the time savings and potential increase in productivity and revenue that deploying SSD can enable. This entry we will focus on the hard cost savings associated with SSD. In the right situation, SSD can actually be less expensive than mechanical drives.The first misnomer when comparing costs between SSD and mechanical drives is often those comparisons are to the cheapest SSD capacity vs. the cheapest drive capacity. This simply is not fair. SSD essentially has two classes of storage; Flash SSD and DRAM SSD and both deliver significantly better performance than tier one mechanical storage.

To get increased performance out of mechanical drives workarounds have been developed that are costly from both a power perspective and a physical assets perspective. Replacing these workarounds with SSD can further increase performance while reducing both power and cooling costs. In reality the price comparison should be to the very high end of tier one mechanical storage and should factor in all of these workarounds that people choose when trying to get the maximum performance out of tier one mechanical storage.

Pulling performance from mechanical drives often follows a path that while it increases performance also increases cost. Typically the first workaround for poor mechanical drive performance is to use standard array sets but with 15k RPM fiber channel drives. If this does not deliver the performance required the next step is to greatly extend the drive count, still using 15k RPM drives, but sometimes tripling or more the original set. These array groups are almost always front ended by fast storage controllers. If the system isn't a virtualized storage system that can perform wide striping, the last resort is to short stroke the drives in the array group, which formats the drives so that only the faster edge of the platter will be written to. While this will increase performance, it also severely reduces the addressable capacity of those drives.

In combination with the above techniques, performance-hungry applications will use a very high server count accessing the storage to increase parallelism. These drive configurations are now well suited to a small number of threads.

The result of all the workarounds is high acquisition, power, and cooling costs and of course a high degree of complexity, especially when compared with SSD. Depending on the environment, a choice needs to be made between Flash-based SSD (read heavy) and DRAM-based SSD (write heavy). Especially in write-heavy environments, only a fraction of the data needs to be mounted on SSD. The result is a significantly smaller disk allocation that requires less power and delivers better performance. All of this then reduces complexity.

When compared with a 50+ 15k RPM drive array that is short stroked, front-ended by multiple storage controllers, and requires a high server count for streaming, SSDs can reduce both CapEx and OpEx now. There is no need to wait for further price drop in memory.

Join us for our upcoming Webcast, SSD: Flash vs. DRAM...and the winner is?

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

Subscribe to our RSS feed.

George Crump is founder of Storage Switzerland, an analyst firm focused on the virtualization and storage marketplaces. It provides strategic consulting and analysis to storage users, suppliers, and integrators. An industry veteran of more than 25 years, Crump has held engineering and sales positions at various IT industry manufacturers and integrators. Prior to Storage Switzerland, he was CTO at one of the nation's largest integrators.

Comment  | 
Print  | 
More Insights
Comments
Threaded  |  Newest First  |  Oldest First
Is Threat Intelligence Garbage?
Chris McDaniels, Chief Information Security Officer of Mosaic451,  5/23/2018
New Mexico Man Sentenced on DDoS, Gun Charges
Dark Reading Staff 5/18/2018
What Israel's Elite Defense Force Unit 8200 Can Teach Security about Diversity
Lital Asher-Dotan, Senior Director, Security Research and Content, Cybereason,  5/21/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: Shhh!  They're watching... And you have a laptop?  
Current Issue
Flash Poll
[Strategic Security Report] Navigating the Threat Intelligence Maze
[Strategic Security Report] Navigating the Threat Intelligence Maze
Most enterprises are using threat intel services, but many are still figuring out how to use the data they're collecting. In this Dark Reading survey we give you a look at what they're doing today - and where they hope to go.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-3018
PUBLISHED: 2018-05-24
The AXIS webapp in deploy-tomcat/axis in IBM Tivoli Application Dependency Discovery Manager (TADDM) 7.1.2 and 7.2.0 through 7.2.1.4 allows remote attackers to obtain sensitive configuration information via a direct request, as demonstrated by happyaxis.jsp. IBM X-Force ID: 84354.
CVE-2013-3023
PUBLISHED: 2018-05-24
IBM Tivoli Application Dependency Discovery Manager (TADDM) 7.1.2 and 7.2.0 through 7.2.1.4 might allow remote attackers to obtain sensitive information about Tomcat credentials by sniffing the network for a session in which HTTP is used. IBM X-Force ID: 84361.
CVE-2013-3024
PUBLISHED: 2018-05-24
IBM WebSphere Application Server (WAS) 8.5 through 8.5.0.2 on UNIX allows local users to gain privileges by leveraging improper process initialization. IBM X-Force ID: 84362.
CVE-2018-5674
PUBLISHED: 2018-05-24
This vulnerability allows remote attackers to execute arbitrary code on vulnerable installations of Foxit Reader before 9.1 and PhantomPDF before 9.1. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw...
CVE-2018-5675
PUBLISHED: 2018-05-24
This vulnerability allows remote attackers to execute arbitrary code on vulnerable installations of Foxit Reader before 9.1 and PhantomPDF before 9.1. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw...