RAID 0 with Nvme or 2 Separate Drives?
12 minutes ago, ChrisLoudon said:Hi guys,
After installing Far Cry 6 on one of my PCs that only has a 256GB NVMe drive, I now have pretty much zero space left.
I have a loft full of old PCs and bits and bobs including matching 256GB NVMe drives so was gonna plonk one in to yield a bit more storage however, I wasn't sure if I should strap them together in Raid 0 or just use the 2nd drive as a D: drive.
Its been a while since I've created a RAID volume for day-to-day use in a PC so wasn't sure what the best practice was these days. I've used RAID 0 in the past on spinning metal and lost a few files along the way.
Its going in a mediocre gaming PC so if the array was to fail there'd be nothing that can't be replaced with ease.
Any advice?
I wouldn't simply for the extra potential latency. When your boot/main drive is in the first M.2 slot, almost always that's wired directly to the CPU's I/O die or Uncore (aka the North Bridge). Almost always, the secondary M.2 slots are wired to the chipset which shares bandwidth with most other PCIe devices, which can be as small as PCIe 4.0 4x or 8x. That then also forces bandwidth to the chipset (South Bridge) to manage that RAID volume.
I ran RAID0 M.2 PCIe 4.0 4x drives pretty early on with an X570 motherboard. I ended up getting rid of it and seemingly noticed a latency benefit. The best I could come up with as an explanation was the lowered complexity of data transport. Where I concluded that the potential increase in latency isnt worth the unnecessarily higher read/write speeds with RAID0. RAID1 is another story which is entirely useful, but that's not applicable here.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now