RAID 0 with two 1 TB NVMe drives: scratch space, not a place to keep data

A stripe of two drives can be faster than one on large sequential transfers. It isn't faster on every workload, many workloads don't see double, and the rest of the system can limit the gain too.

Risk is the cost. The stripe loses everything when either drive fails. At an assumed 2% yearly failure rate per drive, the chance that the stripe loses data in a year is 3.96%. That 2% is a placeholder for planning, not a measured NVMe failure rate.

A single larger NVMe drive gives the same 2 TB with one drive's failure chance, 2%, so the stripe takes on extra risk for its speed.

How much faster a Gen 5 drive is than a Gen 4 drive is a separate question, covered in the Gen 4 vs Gen 5 comparison.

Stripe these drives for scratch space, caches, and temporary render or project files that can be recreated. Keep a backup of anything that matters. RAID isn't a backup: it doesn't protect against deleted files, ransomware, a failed controller or a fire.

Two 1 TB NVMe drives in RAID 0 make sense when the data can be recreated and speed matters. You get 2 TB usable from 2 TB raw with no protection, and the stripe loses everything if either drive dies. Speed is the reason to stripe, and the gain depends on the workload.

If you need space more than speed, a single larger NVMe drive gives the same 2 TB with one drive's failure chance, 2%, against 3.96% for the pair.

Use the stripe for scratch work and caches, keep a backup for everything else, and read the Gen 4 vs Gen 5 comparison if drive generation is what you're weighing.