Aug 24 2017
- last edited on
Apr 15 2021
Hello, Storage Team! I am a consultant (and Microsoft MVP) that sees Hyper-V Replica, Storage Spaces and Storages Spaces Direct as great solutions for my SMB (the protocol and small- to mid-sized businesses). :)
The major issue I've run into is storage performance when using parity. Specifically, write performance can be extremely slow, and rebuild times have made some use cases impractical. Is there any work being done to help with this? I understand that storage tiering (hot/cold tiers) might be one approach, but costs are a major issue for these clients. Any suggestions would be welcome!
Aug 24 2017 09:26 AM
Aug 24 2017 09:50 AM - edited Aug 24 2017 10:32 AMSolution
We have worked to improve rebuild times for Spaces across mirror, parity, and mirror-accelerated parity volumes. These improvements will be available in the Windows Server, Version 1709 release, and some of these improvements have been backported to previous 2016 releases as well. Let us know if you continue to see unsatisfactory rebuild performance, and if so, we'd like to hear more and use your feedback and target scenarios to improve rebuild performance further.
For parity performance in general, we are focusing our efforts on improving the performance of mirror-accelerated parity rather than parity alone. Depending on the size of your working set and the drift of that working set, you can improve your performance dramatically by using SSDs as only 20% or even less of your volume's capacity, which we hope offers a cost-conscious way to improve performance for parity.
Aug 24 2017 10:02 AM
I also recommend checking out this video which discusses design considerations for Storage Spaces Direct, and covers the scenarios when you should use Mirror vs. Miror-accelorated Parity vs. Parity: