News
11/7/2008
08:52 AM
George Crump
George Crump
Commentary
50%
50%

SSD's Latency Impact

In our last entry we talked about latency and what it was. We also discussed how storage system manufacturers are trying to overcome latency and performance issues of mechanical drives by using techniques like making the drives faster by using higher RPM drives, array groups with a high drive count, short-stroking those drives, wide striping those drives, and increasing the number of application servers

In our last entry we talked about latency and what it was. We also discussed how storage system manufacturers are trying to overcome latency and performance issues of mechanical drives by using techniques like making the drives faster by using higher RPM drives, array groups with a high drive count, short-stroking those drives, wide striping those drives, and increasing the number of application servers for improved parallelism.All of these techniques cost money, are not very green, and in many cases are more expensive than simply using SSD. Not to mention that they don't typically come close to SSD performance. The result has been the existence of standalone, purpose-built SSD solutions like those from Texas Memory Systems, Solid Data Systems, and Violin Memory, or the manufacturer adding SSD in a "drive-like" manner to its current storage systems.

The speed of SSD technology, especially DRAM, changes the latency focus away from the actual storage medium, as it has now been optimized, and onto the storage system's infrastructure, which is suddenly a lot slower than the storage media. For vendors that incorporate SSD into existing drive enclosures, the performance of the shelf itself becomes a problem, the performance of the processors in the controllers becomes a problem, and an incorrectly sized cache (too big or too small) becomes a problem.

Another factor is that the software load on the controller becomes an issue. For the past several years, storage manufacturers have been piling on features to the storage controller like snapshots, replication, data deduplication, and others. All of these features take computing resources away from responding to storage I/O requests, which worsens system latency.

The result is that while the SSD technology going into the solution may be fast, simply adding SSD to your storage system may not dramatically improve performance like it should. Standalone, purpose-built SSD systems offer lower latency because these vendors have built systems from the chip up that are designed to deliver on the low latency of SSD.

In our next entry, we will examine those differences and how storage manufacturers will need to alter their delivery of SSD technology. Then we will wrap up with capacity management on SSDs. At the cost of SSD technology, the only good SSD is a FULL SSD.

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
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Flash Poll
10 Recommendations for Outsourcing Security
10 Recommendations for Outsourcing Security
Enterprises today have a wide range of third-party options to help improve their defenses, including MSSPs, auditing and penetration testing, and DDoS protection. But are there situations in which a service provider might actually increase risk?
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2015-0714
Published: 2015-05-02
Multiple cross-site scripting (XSS) vulnerabilities in Cisco Finesse Server 10.0(1), 10.5(1), 10.6(1), and 11.0(1) allow remote attackers to inject arbitrary web script or HTML via unspecified parameters, aka Bug ID CSCut53595.

CVE-2014-3598
Published: 2015-05-01
The Jpeg2KImagePlugin plugin in Pillow before 2.5.3 allows remote attackers to cause a denial of service via a crafted image.

CVE-2014-8361
Published: 2015-05-01
The miniigd SOAP service in Realtek SDK allows remote attackers to execute arbitrary code via a crafted NewInternalClient request.

CVE-2015-0237
Published: 2015-05-01
Red Hat Enterprise Virtualization (RHEV) Manager before 3.5.1 ignores the permission to deny snapshot creation during live storage migration between domains, which allows remote authenticated users to cause a denial of service (prevent host start) by creating a long snapshot chain.

CVE-2015-0257
Published: 2015-05-01
Red Hat Enterprise Virtualization (RHEV) Manager before 3.5.1 uses weak permissions on the directories shared by the ovirt-engine-dwhd service and a plugin during service startup, which allows local users to obtain sensitive information by reading files in the directory.

Dark Reading Radio
Archived Dark Reading Radio
Join security and risk expert John Pironti and Dark Reading Editor-in-Chief Tim Wilson for a live online discussion of the sea-changing shift in security strategy and the many ways it is affecting IT and business.