No one is giving you the dark horse, underdog advice that you should put a spinning hard drive in there too.

Even if you just use it as a backup for your nvme you’ll be happy but spinning drives work great as “worm” disks and will almost always last longer than equivalent flash media. Having a place to put your video and audio files as well as code and other stuff that doesn’t need to go into ram fast as fuck boyee will let you stretch your nvme more as games baloon up to giant size too.

I did this. High capacity hard disk (spinning) drives have gotten pretty cheap, and with the right filesystem, the NVMe can serve as a warm cache in front of the slower HDDs. I’m not sure how it works in practice, but Windows has a feature called “Storage Spaces” to do LVM-like things along these lines. The most sophisticated options are in Windows Server, but I believe it is also available in the higher teir desktop OSes. On Linux, you can use block layer systems like LVM or BCache, or special-purpose multi-disk filesystems like BCacheFS. Not sure if I’d recommend it (for project longevity reasons), but I went the BCacheFS route with 2TB of NVMe backed by 2x6TB HDDs.

It’s definitely worth looking into a solution which merges the physical drives into a logical volume, whether at the block or filesystem level. Rather than just having separate fast and slow filesystems, you can have hot files automatically promoted to the SSD and cold files automatically demoted to the HDD. My setup gives me one single 12TB filesystem with most of the upsides of the NVMe storage. It also allows me to take individual devices out of the array for replacement if e.g. the NVMe wears, or a HDD starts making noise. And because it is implemented at the filesystem layer, things like replication can be configured at the directory level, instead of being all-or-nothing like a traditional RAID or LVM configuration which operate below the filesystem layer.