How to Choose an NVMe SSD for a Homelab or PC in 2026

By LK Wood IV · Published 2026-06-17 · Updated 2026-10-02 · ~10 min read · St. Louis County, MO

NVMe SSD choice is simpler than the market noise suggests. The right drive depends on what you’re using it for — a boot drive for a gaming PC has different requirements than a Proxmox VM storage pool, which has different requirements than NAS cache or a ZFS log device.

This page explains how to choose by role and uses three exact-capacity consumer specifications as examples. If your question is instead where a particular drive sits against the field, the SSD tier list tiers current NVMe drives by PCIe generation, NAND type, cache architecture and rated endurance, with every row cited to a vendor document.

The individual Samsung 990 PRO, Samsung 980 PRO and WD_BLACK SN850X reviews go deeper into capacity, firmware and upgrade decisions. Use those details after deciding what storage role the drive will serve.

Pick the role before the drive

The labels NVMe, Gen4, and Gen5 do not tell you whether a device is safe or fast for a homelab role. Start with what happens when the device loses power or fails, then choose the metric that matches the I/O.

The role distinctions come from the OpenZFS caching documentation, the OpenZFS hardware guide, and the Proxmox VE Administration Guide.

Gen3 vs Gen4 vs Gen5: the real-world difference

Generation is a compatibility and peak-throughput filter. It is not a workload verdict. Compare current exact-model prices only after the role, required features, and motherboard slot are known.

Documented consumer examples for a gaming OS drive

Gaming PC OS drive (1TB)

Samsung 990 Pro 1TB

• Sequential: 7,450/6,900 MB/s (PCIe 4.0 × 4) — Samsung data sheet
• Random IOPS: 1,200K read / 1,550K write (QD32 T16, rated)
• DRAM: Yes (LPDDR4)
• TBW: 600 TBW
• Warranty: 5 years

The Samsung data sheet documents the numbers above for the exact 1TB capacity. They make it a candidate for a gaming or desktop OS drive. They do not establish power-loss safety, steady-state VM latency, or a universal reliability advantage.

WD Black SN850X 1TB

• Sequential: 7,300/6,300 MB/s — WD/SanDisk product page; the 7,300/6,600 figure that gets quoted everywhere is the 2TB and 4TB spec
• TBW: 600 TBW

The WD/SanDisk specification makes the 1TB SN850X another consumer gaming/desktop candidate. Compare current exact model, capacity, seller, condition, firmware, cooling, and price before choosing between it and the 990 Pro.

Crucial P3 Plus 2TB: a legacy/EOL exact-capacity specification example

• Sequential: 5,000/4,200 MB/s (PCIe 4.0) — Crucial product page
• TBW: 440 TBW

The official page now labels this model “CRUCIAL EOL.” It still documents those peak sequential and endurance ratings, but it does not establish steady-state latency or sustained-write behavior. Treat them as legacy comparison inputs rather than a current-buy recommendation or a VM-storage or server endorsement, then measure the intended workload and define the recovery plan.

Best 2TB NVMe and budget decision

The T500 is not the default for long ingest jobs: Tom’s Hardware’s 2TB review found strong general performance but inconsistent sustained-write behavior. None of the cited manufacturer sheets documents the power-loss protection required for a durable SLOG. Apply the role matrix before the peak numbers.

For a budget NVMe SSD, compare the delivered price of the exact capacity on the day you buy. The budget pick is the lowest-cost non-EOL model here that meets the workload, warranty and endurance requirement; it is not automatically the drive with the lowest launch price or highest sequential number. The P3 Plus remains a legacy specification example rather than a current default.

Proxmox server: OS drive + VM storage

Boot drive: size and protect it for the writes the host actually makes

Proxmox continues to write logs, RRD data, configuration, package state, and service data after boot. A lighter host root workload may not need the fastest drive, but it still needs adequate endurance, health monitoring, and a tested recovery path. Mirror the boot/root device when host availability requires it.

VM storage pool: measure latency and decide the failure model

Rated peak IOPS is not enough. Compare steady-state random latency, fsync latency for synchronous workloads, sustained-write behavior, PLP, endurance, temperature, and the mirror or replication design. A consumer 990 Pro or SN850X can serve a light lab whose outage and recovery risk is understood; this guide does not call either one a durable SLOG or enterprise substitute.

For continuous database or logging writes, measure host writes and latency first. Compare the exact capacity’s TBW or DWPD, warranty term, PLP behavior, and sustained benchmark. TBW divided by measured daily writes is a warranty-budget scenario, not an expected failure date; the SSD endurance calculator should be read that way.

NAS build: L2ARC, SLOG, and special vdevs are different jobs

For TrueNAS or a Proxmox ZFS pool serving storage:

L2ARC: Add RAM first, then measure ARC misses and the working set. L2ARC is an optional read cache populated from ARC. Its loss does not lose pool data. Choose capacity and random-read behavior from the measured cache need; do not buy one merely because the pool uses HDDs.

SLOG: Add one only for a workload that issues synchronous writes and benefits in a representative test. OpenZFS calls for low, consistent latency and power-loss protection; a fast consumer sequential specification is not enough. TrueNAS recommends overprovisioning and notes that 16GB can be sufficient for many systems, but size the device to the actual dirty-data window and failure model. Mirror it when continued protection through one device failure is a requirement.

Special vdev: This is permanent pool storage for metadata and, optionally, small blocks. It is not cache. Give it data-vdev-grade redundancy and capacity planning because losing it can lose the pool.

Primary storage: ZFS can use HDDs, SSDs, or NVMe for data vdevs; NVMe is not limited to cache. Choose media from capacity, latency, endurance, power, noise, and recovery requirements. Do not assume every drive in a product family uses helium or carries the same vibration features. Monitor SMART data and keep a separate tested backup regardless of media type.

What I run

My daily rig uses a Samsung 970 EVO Plus 1TB — Gen3, from before Gen4 was the norm. It works fine as a gaming boot drive in 2026 because game load time bottlenecks are rarely sequential throughput. If I were buying new today, I’d buy a Gen4 drive. If I’m upgrading: the 970 EVO Plus stays until it fails.

DRAM is one design input

Dedicated DRAM can help a controller hold its mapping table and sustain predictable behavior. DRAM-less designs can use Host Memory Buffer, and the result still depends on controller, NAND, firmware, capacity, cache state, queue depth, and workload. Do not accept or reject a server drive from the DRAM line alone. Compare steady-state latency and write behavior for the exact model, then apply the role matrix’s PLP, endurance, and redundancy requirements.

Gen5 NVMe: when it makes sense

PCIe 5.0 drives raise the sequential ceiling, but the motherboard must expose a Gen5 M.2 slot and the exact drive’s thermal requirements still apply. CPU generation alone does not prove slot wiring. A heatsink requirement also comes from the exact model and workload, not the interface label.

If you need more drives than the built-in M.2 sockets provide, use the NVMe Expansion Compatibility Checker before choosing an adapter. Its current catalog covers four named ASUS boards and only the cited CPU-group and slot combinations; an unknown board or undocumented lane split stays not documented instead of being inferred from a physical x16 slot.

Gen5 matters when a measured workload is throughput-bound and the candidate drive improves that workload without creating a thermal or sustained-write problem. A database may be latency-bound rather than sequentially bound; a game may wait on decompression or CPU work. Use a named benchmark that matches the task and compare current exact- model prices before paying for the interface.

Capture your workload before buying

1. Record the exact drive model, firmware, capacity, slot/link width, filesystem or ZFS topology, and whether the workload issues synchronous writes. Save smartctl -x output before testing.
2. For a Proxmox host, run pveperf as a broad host check. For a replaceable test file on the target dataset, use fio with a data set larger than RAM and the drive’s short burst cache. Never point a destructive job at a raw device that contains data.
3. Match the job to the decision: random read for cache candidates, mixed random I/O for VM storage, and fsync=1 or an equivalent synchronous test for a SLOG decision. Record queue depth, block size, runtime, direct-I/O mode, and whether the drive reached steady state.
4. Read latency percentiles alongside throughput. A higher peak with worse p99/p99.9 latency can make interactive VMs feel worse. Re-read SMART temperature, media/data-integrity errors, percentage used, unsafe shutdowns, and data written after the run.
5. Change one variable at a time and repeat. Keep a result only when the raw command, output, hardware identity, and topology travel together.

Sources

Every capacity, throughput and endurance figure here comes from the manufacturer’s own specification for the exact capacity named. That distinction earns its keep. Two numbers this guide used to carry were the wrong capacity’s spec.

• Samsung — SSD 990 PRO Data Sheet, Rev. 2.0 (PDF). The 1TB column: sequential 7,450 / 6,900 MB/s, random 1,200K read / 1,550K write at QD32 T16, 1GB LPDDR4 cache, 600TB TBW, 5-year limited warranty. The widely repeated 1,400K random read is the 2TB column.
• Western Digital / SanDisk — WD_BLACK SN850X product page, model WDS100T2X0E: 1TB is 7,300 MB/s read and 6,300 MB/s write, 600 TBW, 5-year limited warranty. WD’s own product comparison chart (PDF) states the 7,300 / 6,600 pair applies to “2TB and 4TB models only”.
• Crucial / Micron — P3 Plus 2TB product page, marked EOL: CT2000P3PSSD8, sequential 5,000 / 4,200 MB/s, SSD endurance 440TB.
• Proxmox — Proxmox VE Administration Guide: storage architecture and enterprise-SSD guidance for serious storage roles.
• OpenZFS — ARC, L2ARC, SLOG and special-vdev roles and hardware guidance.
• TrueNAS — SLOG reference (last modified 2026-03-02) and L2ARC reference (last modified 2025-12-10).

The four product specification documents were fetched and read on 2026-08-23. The platform/storage references were re-read on 2026-09-26. This page does not publish a current price table; verify the exact model, capacity, seller, condition, stock, and price at purchase time.

For the homelab server foundation, the ZFS on Proxmox guide covers pool configuration and ARC tuning that matters more than drive generation in most storage scenarios. For NVMe in a gaming build context, the Gaming PC Build 2026 lists storage picks alongside the full component selection.