What you will learn from this tip:
How to improve SAN performance.
Storage area networks (SANs) are complicated, and how crucial SAN components are configured affects SAN performance....
By submitting your email address, you agree to receive emails regarding relevant topic offers from TechTarget and its partners. You can withdraw your consent at any time. Contact TechTarget at 275 Grove Street, Newton, MA.
Questions about SAN performance tuning keep coming to the Ask the Expert section of SearchStorage.com. It seems as if many shops are currently trying to figure out ways to squeeze some more performance out of their SANs.
"People may have implemented SANs and storage and now want to tune or get better performance," says
, founder and senior analyst of StorageIO. "Or the initial systems they deployed may have been under-configured or outgrown." According to Schulz, there are other factors that may explain this spike of interest in performance tuning.
A bottleneck may have shifted from one location to another in the course of an upgrade or new technology acquisition.
Workload increases (demand) are outpacing the available resources and performance.
Awareness of adequate performance and its impact on service level requirements -- looking beyond just storage capacity and cost per gigabyte.
People have to do more with less, this also means trying to increase storage capacity utilization that can result in performance problems.
Many acquisitions are centered around capacity or number of ports and do not take into perspective the bigger picture of latency and performance.
Whatever their reasons, storage pros want information on how to get their SAN running wide open. Check out the expert technical advice below to learn how to get the most out of your SAN.
Troubleshooting McData 2640 SAN router issues
HBAs: Are dual HBAs worth the investment?
Performance monitoring on boot from SAN
How to minimize I/O latency
iSCSI, iFCP and FCIP: How do they stack up?
Do you know…
How to get the most from your storage?
This Content Component encountered an error