Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

News

11/5/2008
02:55 PM
George Crump
George Crump
Commentary
50%
50%

SSDs Are All About Latency

Nearly every storage manufacturer has been articulating a solid state disk (SSD) strategy in the past two quarters. EMC, HP, IBM, HDS, NetApp, and Compellent are all set to add the capability to their offering. Some are doing so today, while others are still in the strategy mapping process.

Nearly every storage manufacturer has been articulating a solid state disk (SSD) strategy in the past two quarters. EMC, HP, IBM, HDS, NetApp, and Compellent are all set to add the capability to their offering. Some are doing so today, while others are still in the strategy mapping process.What most of them agree on is that SSDs can be a game changer, with the potential performance improvements of 30X when compared with mechanical drives. A key issue for them and you to understand is latency.

First, what is latency? Also called response time or wait time, in storage terms it is the amount of time between a request being made and that request being fulfilled. A user example would be the amount of time it takes from you launching your word processor to you being able to start typing.

For most applications, standard mechanical hard drives fulfill these requests fast enough that this response time isn't even noticed, but sticking with the word processing example, what if as you started to type your novel, you had to wait two seconds between the time you press a letter and the time that you could press the next letter? That would get annoying real fast and it would cost you time and probably money. Your important revenue generating application treats response time the same way.

So what makes the latency of various storage systems different? In the past it had all been about the speed of the drives. Everything else in the storage system was able to respond faster than the drives so the focus became 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.

SSDs change that focus, the speed of the drive is no longer the issue. SSDs change the latency focus on the storage system itself and away from the drive. Manufacturers will need to change how these SSD shelves are addressed or create standalone systems like those from Texas Memory Systems, Solid Data Systems, and Violin Memory.

In our next entry we will take a deeper dive into the impact on storage systems as a result of zero latency at the drive level.

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
Newest First  |  Oldest First  |  Threaded View
DevSecOps: The Answer to the Cloud Security Skills Gap
Lamont Orange, Chief Information Security Officer at Netskope,  11/15/2019
Attackers' Costs Increasing as Businesses Focus on Security
Robert Lemos, Contributing Writer,  11/15/2019
Human Nature vs. AI: A False Dichotomy?
John McClurg, Sr. VP & CISO, BlackBerry,  11/18/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: -when I told you that our cyber-defense was from another age
Current Issue
Navigating the Deluge of Security Data
In this Tech Digest, Dark Reading shares the experiences of some top security practitioners as they navigate volumes of security data. We examine some examples of how enterprises can cull this data to find the clues they need.
Flash Poll
Rethinking Enterprise Data Defense
Rethinking Enterprise Data Defense
Frustrated with recurring intrusions and breaches, cybersecurity professionals are questioning some of the industrys conventional wisdom. Heres a look at what theyre thinking about.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2011-3350
PUBLISHED: 2019-11-19
masqmail 0.2.21 through 0.2.30 improperly calls seteuid() in src/log.c and src/masqmail.c that results in improper privilege dropping.
CVE-2011-3352
PUBLISHED: 2019-11-19
Zikula 1.3.0 build #3168 and probably prior has XSS flaw due to improper sanitization of the 'themename' parameter by setting default, modifying and deleting themes. A remote attacker with Zikula administrator privilege could use this flaw to execute arbitrary HTML or web script code in the context ...
CVE-2011-3349
PUBLISHED: 2019-11-19
lightdm before 0.9.6 writes in .dmrc and Xauthority files using root permissions while the files are in user controlled folders. A local user can overwrite root-owned files via a symlink, which can allow possible privilege escalation.
CVE-2019-10080
PUBLISHED: 2019-11-19
The XMLFileLookupService in NiFi versions 1.3.0 to 1.9.2 allowed trusted users to inadvertently configure a potentially malicious XML file. The XML file has the ability to make external calls to services (via XXE) and reveal information such as the versions of Java, Jersey, and Apache that the NiFI ...
CVE-2019-10083
PUBLISHED: 2019-11-19
When updating a Process Group via the API in NiFi versions 1.3.0 to 1.9.2, the response to the request includes all of its contents (at the top most level, not recursively). The response included details about processors and controller services which the user may not have had read access to.