One of the â€œkey featuresâ€ of XIV is the wide striping of data across all spindles, a concept weâ€™re seeing more and more. Have you ever wondered what the point is?
I’ve read with interest this week the posts on wide striping and the consequent expansion to thin provisioning. Â Here are some of the highlights:
First there’s Martin Glasborow’s post, which discusses whether wide striping and thin provisioning should be chargeable items. Â I’d go a step further than Martin and suggest that thin provisioning (TP) should also […]
Wide-striping is now just another feature; itâ€™s a very important feature but just another feature now. 3Par took wide striping and made it useable; EMCâ€™s historic implementation using metas and hypers was painful and with the large arrays of today it becomes a full time job to performance manage an array. 3Par made it easy and much kudos to them for doing so. I think 3Parâ€™s legacy will be the ease of management that they have brought to the Enterprise array (and thin provisioning).
The first storage performance horseman is spindles: If you donâ€™t have enough disk units, performance will suffer. I have been laying out storage on enterprise arrays since the dark ages, and one of the first lessons I learned was allocating data to avoid hotspots. I remember spending hours back in the 1990â€™s hunched over custom Excel spreadsheets trying to get my storage layout just right, balancing the workload across every available disk.