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

10/14/2009
08:52 AM
George Crump
George Crump
Commentary
50%
50%

Understanding Storage Controller Performance

Storage controllers are the engine that drives the storage system you own. They are essentially a compute engine for storage arrays. Understanding storage controller performance and what can impact storage controllers is an important step in the optimization of your storage environment. It is also something that many storage managers assume is good enough.

Storage controllers are the engine that drives the storage system you own. They are essentially a compute engine for storage arrays. Understanding storage controller performance and what can impact storage controllers is an important step in the optimization of your storage environment. It is also something that many storage managers assume is good enough.Storage controller's performance can be impacted by a host of circumstances. Today's storage systems are asked to do so much more than the first external SCSI arrays. First, they manage significantly more capacity and drive quantity. Capabilities like snapshots, replication and the RAID calculation all impact the storage controller. Further new features like thin provisioning are just adding to the problem. This is why so many storage systems hit maximum performance at about 1/2 the drive population than the brochure states.

Second, storage systems are no longer responsible for servicing the requests of a single server. In shared environments the storage controllers can be responding to dozens if not hundreds of attached servers and workstations. To compound the issue, many environments, thanks to server virtualization, will have multiple server instances making multiple storage I/O requests from a single host. This leads to extremely random and unpredictable workloads in the environment which can saturate controllers.

Today's storage controllers are responding to requests from more performance hungry servers that are attached to them. In web applications for example the storage may be responding to thousands of simultaneous users all accessing the same database or randomly each accessing different photos. Again, in virtualized server environments, these demands can come from 1,000 VMs spread out across a few hundred physical systems.

The classic dual controller architecture itself is misleading. In many cases both controllers are not equally handling the storage I/O for a given RAID volume. Usually one is assigned as the primary and the other as the secondary. The secondary is only used if the primary fails. The result is a single controller, handling all the above highly random conditions, can more realistically get saturated.

The classic response has been to overbuy storage compute muscle. The problem with this is that we all know that today's processors will be replaced by tomorrow's for less money. When you overbuy processing you are paying extra for compute muscle that you may not need until next year or later.

This has lead to some of the major manufacturers following the lead of a few storage innovators to start delivering clustered storage systems. Although how these clusters are assembled and the services they offer vary, they address the storage controller performance bottleneck that we detail in our article "What's Causing the Storage I/O Bottleneck?".

These systems allow continuous scale of capacity, I/O bandwidth as well as storage compute performance. Not every data center is going to encounter storage controller performance issues, and for those data centers standard systems are more than acceptable, but if your data center can cause any of the above conditions then storage controllers are something you need to pay attention to.

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

Subscribe to our RSS feed.

George Crump is lead analyst of Storage Switzerland, an IT analyst firm focused on the storage and virtualization segments. Find Storage Switzerland's disclosure statement here.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Commentary
Ransomware Is Not the Problem
Adam Shostack, Consultant, Entrepreneur, Technologist, Game Designer,  6/9/2021
Edge-DRsplash-11-edge-ask-the-experts
How Can I Test the Security of My Home-Office Employees' Routers?
John Bock, Senior Research Scientist,  6/7/2021
News
New Ransomware Group Claiming Connection to REvil Gang Surfaces
Jai Vijayan, Contributing Writer,  6/10/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: Google's new See No Evil policy......
Current Issue
The State of Cybersecurity Incident Response
In this report learn how enterprises are building their incident response teams and processes, how they research potential compromises, how they respond to new breaches, and what tools and processes they use to remediate problems and improve their cyber defenses for the future.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-31664
PUBLISHED: 2021-06-18
RIOT-OS 2021.01 before commit 44741ff99f7a71df45420635b238b9c22093647a contains a buffer overflow which could allow attackers to obtain sensitive information.
CVE-2021-33185
PUBLISHED: 2021-06-18
SerenityOS contains a buffer overflow in the set_range test in TestBitmap which could allow attackers to obtain sensitive information.
CVE-2021-33186
PUBLISHED: 2021-06-18
SerenityOS in test-crypto.cpp contains a stack buffer overflow which could allow attackers to obtain sensitive information.
CVE-2021-31272
PUBLISHED: 2021-06-18
SerenityOS before commit 3844e8569689dd476064a0759d704bc64fb3ca2c contains a directory traversal vulnerability in tar/unzip that may lead to command execution or privilege escalation.
CVE-2021-31660
PUBLISHED: 2021-06-18
RIOT-OS 2021.01 before commit 85da504d2dc30188b89f44c3276fc5a25b31251f contains a buffer overflow which could allow attackers to obtain sensitive information.