this post was submitted on 03 Aug 2023
12 points (83.3% liked)
Linux Gaming
15289 readers
142 users here now
Discussions and news about gaming on the GNU/Linux family of operating systems (including the Steam Deck). Potentially a $HOME away from home for disgruntled /r/linux_gaming denizens of the redditarian demesne.
This page can be subscribed to via RSS.
Original /r/linux_gaming pengwing by uoou.
Resources
WWW:
Discord:
IRC:
Matrix:
Telegram:
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Dual booting to a single drive(or an array) is a recipe for disaster. You'd be much better off putting each OS on it's own separate drive, and setting arch as the boot distro since grub will allow you to switch to windows if need be. Windows has a tendency to screw with boot partitions so it's more trouble than it's worth to install it "alongside" on a single drive/raided drives.
RAID0 on nvme barely does anything anyways(especially for gaming,) if anything it's worse as it makes some of the lower que depth operations(and latency) slower.
So to your question, you can in theory, but ideally you shouldn't.
I actually benchmarked my Samsung 980 Pro M.2 Raid 0 setup vs a single. While sequential read-write is between 2-3* better, random is exactly the same except for 1.8* better random write speed.
Which is why you generally don't want NVME raid. You'll never, ever use that much sequential in a consumer environment, and game loading mostly uses random reads rather than sequential. What makes an OS feel snappy and responsive is the lower que depths(i.e q1t1,) which actually get worse or stay about the same when you raid flash together.
The only time i feel like raiding them together is worth it is if you're lazy and want one big storage blob, or if you have unique circumstances that demand ridiculous amounts of ingest speed, like with 4k footage.