How much storage I/O performance do you want vs. need?
The answer to how much storage I/O performance you need vs. want probably depends on cost, for which applications along with benefit among other things.
Here is an excerpt:
Can storage speed be too fast? Or, put another away, how do you decide a return on investments or innovation from the financial resources you spend on storage and the various technologies that go into storage performance.
Think about it: Fast storage needs fast servers, IO and networking interfaces, software, firmware, hypervisors, operating systems, drivers, and a file system or database, along with applications. Then there are the other buzzword bingo technologies that are also factors, among them fast storage DRAM and flash Solid State Devices (SSD).
Some questions to ask about storage I/O performance include among others:
- How do response time, latency, and think or wait-times effect your environment and applications?
- Do you know the location of your storage or data center performance bottlenecks?
- If you remove bottlenecks in storage systems or appliances as well as in the data path, how will your application or the CPU in the server it runs on behave?
- If your application server is currently showing high CPU due to the system overhead of having to wait for storage I/Os, you may see a positive improvement.
- If more real work can be done now, will all of the components be ready to support each other without creating a new bottleneck?
- Also speaking of storage I/O performance, how about can we get a side of context with them IOPs and other metrics that matter!
So how about it, how much performance, for primary, secondary, backup, cloud or virtual storage do you want vs. need?
Ok, nuff said for now.
All Comments, (C) and (TM) belong to their owners/posters, Other content (C) Copyright 2006-2014 StorageIO All Rights Reserved