1.)Connectivity - Ensure bottlenecks do not exist inside your SAN fabric. Often we find customers who have 4Gbps disk systems connecting to 2Gbps SAN switches or HBAs. A smart notion is to speedily review all pieces of your SAN fabric to identify possible bottlenecks.
2.)Drive Count - System performance is typically easily fixed by adding extra disk drives to the storage configuration. The reason this fix works is that by spreading out the workload, you gain the benefit of having more drives/arms/spindles accessing and retrieving data, and feeding that data to the storage controller.
3.)Drive Size - By using smaller faster drives for high performance environments including Oracle, you avoid disk drive contention. Contention can manifest itself when too much data is placed on bigger drives. An example could be trying to place 2.5TB of data on 10x 300GB Drives.
4.)Drive Type - SATA drives are an superb format for archive or low I/O applications such as file servers or imaging, but grow to be less ideal for larger VMWare, Oracle or Exchange Environments. Make certain you invest within the proper technology according to application and workload
5.)Controller Segregation - As storage requirements continue to grow, small storage shops can eventually morph into significant storage shops. If several high efficiency applications are placed on a single modular array it may possibly overwhelm the program. Think about a second array or a tiered architecture ought to your array have a high combination of performance-oriented applications
6.)RAID Level - Raid 10, Raid 1, Raid 6, RAID-DP, Raid5 and other parity combinations all have their strength and limitations. Do your research to make sure the RAID configuration you're taking into consideration will support and maintain application efficiency for the lengthy term.
Speak with an experienced information specialist today, they can assist you to reduce the cost and complexity of constructing high performing storage environments.
2.)Drive Count - System performance is typically easily fixed by adding extra disk drives to the storage configuration. The reason this fix works is that by spreading out the workload, you gain the benefit of having more drives/arms/spindles accessing and retrieving data, and feeding that data to the storage controller.
3.)Drive Size - By using smaller faster drives for high performance environments including Oracle, you avoid disk drive contention. Contention can manifest itself when too much data is placed on bigger drives. An example could be trying to place 2.5TB of data on 10x 300GB Drives.
4.)Drive Type - SATA drives are an superb format for archive or low I/O applications such as file servers or imaging, but grow to be less ideal for larger VMWare, Oracle or Exchange Environments. Make certain you invest within the proper technology according to application and workload
5.)Controller Segregation - As storage requirements continue to grow, small storage shops can eventually morph into significant storage shops. If several high efficiency applications are placed on a single modular array it may possibly overwhelm the program. Think about a second array or a tiered architecture ought to your array have a high combination of performance-oriented applications
6.)RAID Level - Raid 10, Raid 1, Raid 6, RAID-DP, Raid5 and other parity combinations all have their strength and limitations. Do your research to make sure the RAID configuration you're taking into consideration will support and maintain application efficiency for the lengthy term.
Speak with an experienced information specialist today, they can assist you to reduce the cost and complexity of constructing high performing storage environments.
About the Author:
If you're in the market for IBM Storage or EMC Storage, we're the best seller for all your technology storage needs. You'll save hundreds on good quality refurbished and new hardware equipment.
Không có nhận xét nào:
Đăng nhận xét