Administrator-level storage selection concepts. Use the exact model’s current datasheet, firmware support and workload qualification before purchase.
Stuart Kerr Spindlow has confirmed personal use and testing of the software covered by Happy SysAdm. The assessments here distinguish documented behaviour from measured results; worked scenarios are labelled and are not personal test records.Separate interface from form factor
Choose an SSD for its supported interface, sustained workload and durability requirements before comparing headline sequential throughput. A SATA model may be sufficient when the application or network is the limit; a compatible NVMe path matters more when local I/O concurrency is the constraint. For write-heavy systems, endurance and documented power-loss behaviour can be more important than the largest burst number.
SATA and PCIe describe different transport paths; NVMe is a protocol commonly used over PCIe. A physical form such as M.2 does not by itself tell you the interface, keying, lane allocation or boot support. Confirm the server or enclosure’s supported combinations.
Identify whether the workload is dominated by large sequential transfers, small random operations or mixed reads and writes. Queue depth, block size and concurrency affect benchmark results. A number measured under one pattern cannot be assumed for another.
Read these specifications separately
- Physical form
- M.2 or another form describes the physical package; check keying and platform support.
- Transport and protocol
- Verify SATA versus PCIe and the applicable protocol. Do not infer it from the shape.
- Endurance and workload
- Read TBW or DWPD with capacity, warranty period and workload assumptions.
Read endurance in context
TBW expresses a rated quantity of writes; DWPD expresses drive writes per day over a stated period. Compare them alongside capacity, warranty conditions and the vendor’s workload assumptions. They are not predictions of the exact moment a drive will fail.
Estimate actual host writes and growth rather than sizing solely from current used capacity. Database logs, virtualisation and repeated temporary writes can have very different patterns. Keep a reserve for operational growth and monitor the model-specific health indicators.
Look beyond the headline benchmark
Ask about sustained behaviour after caches fill, latency under the intended workload and thermal limits. For systems that depend on durable writes, evaluate the documented power-loss protection and the complete storage stack’s write guarantees. A consumer label or enterprise label alone is insufficient evidence.
Check firmware support, replacement availability and compatibility with the controller or hypervisor. Do not disable protective flush or write-through behaviour merely to improve a test number; that can change the durability assumptions of the application.
Measure and maintain the deployed system
Use a representative non-destructive test with a clear data set and measurement method. Record whether the result is cached, the workload mix and the state of the array. Avoid write-heavy benchmarks on production volumes without a planned window and recovery protection.
Monitor health, temperature, error trends and actual latency. Keep verified backups regardless of endurance ratings or redundancy. A healthy-looking SSD can still be lost through controller failure, deletion or a broader incident.
Convert an endurance rating into a comparable daily allowance
Kingston explains DWPD as endurance divided by capacity and warranty duration. Using its illustrative 1.92 TB capacity and 3,504 TBW, with an explicitly assumed five-year rating period, 3,504 ÷ (1.92 × 365 × 5) equals 1 drive write per day. That corresponds to an average 1.92 TB of host writes per day under the stated rating convention.
This is a calculation from a vendor’s example, using 365 days per year, not a drive-life measurement or guarantee that the SSD fails immediately beyond that amount. Keep decimal TB units consistent and check the actual model’s warranty conditions. No read or write speed winner follows from endurance alone.