Data storage for the cloud ce11


Published on

Xiotech - Storage for the Cloud

Published in: Education
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Data storage for the cloud ce11

  1. 1. Jim McDonald<br />Chief Strategy Officer, Xiotech<br />Data Storage for the CloudBalancing Performance, Capacity and Cost<br />
  2. 2. Most data follows a similar pattern<br />Write, read, ignore<br />“Small” amounts of data follow a much more aggressive pattern<br />Write, write,read, write,read, read, write, read,read, read,write, write, write, write,read, write<br />The result is that for effective cloud storage you need to have both high capacity and highperformance<br />And it needs to be cheaper than could be done in-house<br />Storage for the Cloud<br />
  3. 3. Traditional cloud storage was viewed as a data dumping ground<br />All about $/GB, performance “irrelevant”<br />Cloud storage is now becoming a lot more active:<br />File synchronisation<br />Big data<br />Calendars<br />…<br />And performance is needed for cloud computing<br />If it can’t do it faster and cheaper it won’t win<br />Why are the Requirements Changing?<br />
  4. 4. An Unfortunate Side-effect of Capacity Growth<br />
  5. 5. Over the past 10 years, on a performance/GB basis, drives have gone down 50x<br />What Does This Mean?<br />
  6. 6. A standard enterprise drive can handle roughly:<br />An Exchange server with 125 users @ 2.4GB/user<br />A 300GB database with 12 transactions per second<br />A virtual desktop implementation with 3 users @ 100GB/user<br />The capacity Vs. performance numbers are very imbalanced against performance<br />For internal IT this is wasted expenditure<br />For cloud service providers this is unobtainable revenue<br />Performance is the Limiting Factor<br />
  7. 7. Snapshots<br />Thin provisioning<br />Deduplication (not compression)<br />Traditional tiering<br />Housekeeping<br />Things which Lower Performance<br />
  8. 8. Traditional tiering is a great example of sacrificing performance for capacity<br />Because tiering focuses on capacity<br />Current tiering algorithms are especially bad for heavily-loaded environments<br />Think sat nav before traffic information<br />Enterprise storage:<br />10,000 IOPS<br />Traditional Tiering<br />Archive storage:<br />2,000 IOPS<br />Performance<br />Current tiering solutions are fine if you just want capacity<br />(But if you just want capacity don’t bother with tiering)<br />
  9. 9. Add disks<br />Fine, as long as you don’t use the capacity<br />Increase the performance per disk<br />Cache (sometimes)<br />Better understanding of drives<br />Intelligent data placement algorithms<br />Tier for performance<br />Use all of the performance of all of the drives<br />How to Fix This:Increase Performance<br />
  10. 10. Cloud test suite provides clean copies of every current version of Microsoft Windows<br />Desktop and server, all language patches, all valid combinations of patches (several thousand instances)<br />Automatically uploads program and runs tests, stores results in centralised area, then destroys the VMs<br />Performance is the enabler:<br />The time taken to create and destroy the VMs is at the cost of the service provider and not the customer<br />So if it can be reduced the service provider makes more money<br />The time taken to run the tests is a fixed rate<br />So if it can be reduced the service provider makes more money<br />Example:Cloud Test Suite<br />
  11. 11. Stop thinking like it’s 2000<br />“If I could get all the old data off my enterprise drives I’d be rich”<br />Capacity is not expensive any more, performance is<br />Measure anything other than archive storage in terms of performance not capacity<br />Be wary of capacity-increasing (and performance-decreasing) “added value” features<br />Do you really need more capacity and less performance?<br />Closing Thoughts<br />
  12. 12. Questions?<br />
  13. 13. Thank You<br />