News
11/5/2008
02:55 PM
George Crump
George Crump
Commentary
Connect Directly
RSS
E-Mail
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
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Flash Poll
Threat Intel Today
Threat Intel Today
The 397 respondents to our new survey buy into using intel to stay ahead of attackers: 85% say threat intelligence plays some role in their IT security strategies, and many of them subscribe to two or more third-party feeds; 10% leverage five or more.
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-2595
Published: 2014-08-31
The device-initialization functionality in the MSM camera driver for the Linux kernel 2.6.x and 3.x, as used in Qualcomm Innovation Center (QuIC) Android contributions for MSM devices and other products, enables MSM_CAM_IOCTL_SET_MEM_MAP_INFO ioctl calls for an unrestricted mmap interface, which all...

CVE-2013-2597
Published: 2014-08-31
Stack-based buffer overflow in the acdb_ioctl function in audio_acdb.c in the acdb audio driver for the Linux kernel 2.6.x and 3.x, as used in Qualcomm Innovation Center (QuIC) Android contributions for MSM devices and other products, allows attackers to gain privileges via an application that lever...

CVE-2013-2598
Published: 2014-08-31
app/aboot/aboot.c in the Little Kernel (LK) bootloader, as distributed with Qualcomm Innovation Center (QuIC) Android contributions for MSM devices and other products, allows attackers to overwrite signature-verification code via crafted boot-image load-destination header values that specify memory ...

CVE-2013-2599
Published: 2014-08-31
A certain Qualcomm Innovation Center (QuIC) patch to the NativeDaemonConnector class in services/java/com/android/server/NativeDaemonConnector.java in Code Aurora Forum (CAF) releases of Android 4.1.x through 4.3.x enables debug logging, which allows attackers to obtain sensitive disk-encryption pas...

CVE-2013-6124
Published: 2014-08-31
The Qualcomm Innovation Center (QuIC) init scripts in Code Aurora Forum (CAF) releases of Android 4.1.x through 4.4.x allow local users to modify file metadata via a symlink attack on a file accessed by a (1) chown or (2) chmod command, as demonstrated by changing the permissions of an arbitrary fil...

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
This episode of Dark Reading Radio looks at infosec security from the big enterprise POV with interviews featuring Ron Plesco, Cyber Investigations, Intelligence & Analytics at KPMG; and Chris Inglis & Chris Bell of Securonix.