250 means you are using flash media. With HDD's performance is completely unacceptable.
250 for SSD writes is probably normal, NVMe would be somewhat faster.
The RAID 0 alternative recommendation was for HDD's.
250 means you are using flash media. With HDD's performance is completely unacceptable.
250 for SSD writes is probably normal, NVMe would be somewhat faster.
The RAID 0 alternative recommendation was for HDD's.
250MB/s across 4 SSDs in a RAID 5 is normal? The same configuration does 1GB/s on unencrypted APFS volumes.
@softraid-support What if I'm on MacOS Catalina where there is native encrypted HFS support? Is there a workaround? I tried to force it using terminal subdividing the RAID 5 volume and inserting a GPT slice so that I can utilize native CoreStorage, but the GPT slice never remained. I'd read elsewhere on the forum that you were experimenting with implementing with implementing encrypted HFS, but that it's a rather difficult workaround?
We have tried working around this, but no, we have not made progress. It may not be possible, unless Apple makes an update to HFS+ or Core Storage.
RAID 0 is an option, which has the issue of not being redundant. RAID 1+0 also.
@softraid-support Got it. And re: "unit stripe size" on encrypted APFS RAID 5 volumes utilizing 8TB HDDs, if I'm primarily dealing with larger files (30-100GB), what's the best choice? 16 KB or 64 KB?
64k was added for better Windows performance, it does not really matter on MacOS, in any testing I have done. So leave the default 16k
@softraid-support Did some testing on a 2012 Mac running MacOS Catalina: sustained writes were much slower with the 64 KB unit stripe size across four 8 TB HDDs in a ThunderBay 4 (TB2 version) configured as RAID 5.
No, this change is likely to require a MacOS change its not there.

