We are digital librarians. Among us are represented the various reasons to keep data -- legal requirements, competitive requirements, uncertainty of permanence of cloud services, distaste for transmitting your data externally (e.g. government or corporate espionage), cultural and familial archivists, internet collapse preppers, and people who do it themselves so they're sure it's done right. Everyone has their reasons for curating the data they have decided to keep (either forever or For A Damn Long Time (tm) ). Along the way we have sought out like-minded individuals to exchange strategies, war stories, and cautionary tales of failures.
There is no such thing as "RAID 5" with Storage Spaces, it's just "Storage Spaces with Parity"
You will have to set up your appropriate columns and block size using Powershell. I don't have any links handy but start searching up Storage Spaces Columns Powershell.
I made several attempts and never got it working well. It's honestly best left to Enterprise setups who know wtf they're doing. That, and I'm not too bright either, so maybe that's a problem too. LOL.
I can’t figure out the columns and allocation with refs the write is always fast then 0 then fast then 0
Honestly, with Storage Spaces you won't get any performance, as well as, reliability. First of all, parity option with storage spaces will lose your data, unless you have reliable backups.
You can try to go with stablebit drivepool + snapraid and check the performance, at least it is simply more reliable. Otherwise, to get a decent performance use hardware RAID or linux mdadm.
Why would you move from a Free, Open-Source solution to a Non-Free, Closed source solution?