Has anyone tried making a striped RAID with one SATA3 SSD and one M.2 NVMe SSD (rather than buy a larger SSD)? If so, what is the net result, does it default to SATA3 speeds or does the r/w speed depend on which drive is being written to at any given time? Thanks.
@PliSsK,
Why would even want to do that ?
Creating a RAID 0 using a fast interface (NVMe) and a slow interface (SATA-3) would completely negate the whole point of RAID 0 which is to increase read/write speeds as the whole process would be slowed down by the SATA-3 SSD.
Some background information ...
All data is split into blocks, be it system files, applications or user data, the block size is defined when creating a RAID, if it's going to be for lots of small files (like an OS) then the block size can be as small as 4K, if its going to be only used for say large video files then the block size can be set to something like 512K
RAID 0 alternates the writing of all data blocks between the two drives :-
1st block to drive 0
2nd block to drive 1
3rd block to drive 0
4the block to drive 1
.... and so on.
So with RAID 0 every file has blocks saved on both drives, this means when reading a file blocks can read from both drives at the same time resulting in a greater read speed than a single drive. However blocks must be read concurrently so in this instance the NVMe SSD would be constantly waiting for the SATA-3 SSD to catch up.
RAID 0 expects two drives of the same type and size ...
Whilst it may still work (assuming MacOS even lets you create such a RAID 0) there would be no benefit speed wise and due to the different interface technologies a RAID 0 made up of a NVMe and a SATA-3 SSD would be IMO quite fragile and highly
NOT recommended.
Cheers
Jay