Windows – What are the options to speed up write speed for Storage Spaces using parity

storage-spaceswindows 10

I'm wondering what my options are for speeding up the write speed to my storage spaces that's using parity.

Setup

  • Windows 10 64-bit verison 1607
  • Intel i7-7700k
  • 16 GB memory
  • Samsung 960 EVO
  • 6x 6 TB Western Digital Red (5200rpm)

I set up the storage space using PowerShell because I was attempting to do ReFS with parity, and though it's an option in the GUI, the GUI was giving me trouble. Format-Volume said "the specified file system is not supported." So, it's an NTFS volume at 26.1 TB, provisioning type is fixed, resiliency is parital, physical disk redundancy is 1.

Transfer Speeds

  • Other Windows 10 64x PC –> Storage space = ~45 MB/s
  • NAS –> Storage space = ~45 MB/s
  • Samsung 960 EVO –> Storage space = ~45 MB/s
  • Storage space –> Samsung 960 EVO = ~610 MB/s

During transfers I see about 1.5 GB of memory in use, and only 3-4% CPU. I've read that you can tell the storage space it's connected to a battery backup (the computer is plugged into a UPS) or use an SSD cache array, but I don't know the pros and cons here, nor the PowerShell commands to do so. I assume the write performance should be a little better than this, right? With such a powerful processor, I wouldn't expect parity calculations to slow it down too much.

Best Answer

It's a bad idea to use file copy as a progress indicator of anything. Stick with DiskSPD or you'll get random & unreproducible numbers.

https://blogs.technet.microsoft.com/josebda/2014/08/18/using-file-copy-to-measure-storage-performance-why-its-not-a-good-idea-and-what-you-should-do-instead/

You can use Windows built-in SSD based caching software or configure tiered storage spaces where your SSD will act as a WBC or performance tier.

https://blogs.technet.microsoft.com/askpfeplat/2013/10/20/storage-spaces-how-to-configure-storage-tiers-with-windows-server-2012-r2/

https://msdn.microsoft.com/en-us/library/windows/hardware/dn567634(v=vs.85).aspx

I'd suggest NOT to use any third-party DRAM & SSD cache.

Related Question