Technology card
ShippingConsumer SSD
client SSD · retail SSD · consumer solid-state drive
Read a client SSD specification: distinguish cache-assisted writes, sustained performance, endurance ratings and power-loss behavior.
Glossary entry on hesela.dev · JSON record · SLC cache · Testing steady state · Mapping-cache behavior · Synchronization and errors · Power-fault evidence and limits
Related
On this page6 sections
In one minute
A consumer SSD is a solid-state drive intended for personal computers and other client systems, with capabilities that must be established for the particular model.
Client is an application category. SNIA's performance specification places personal desktop and laptop use in this category and distinguishes it from shared enterprise environments. That classification does not select SATA versus NVMe, a NAND cell type or a power-loss protection design. Read the product's interface and mechanical requirements separately. [1]
Start with the conditions behind a write-speed claim. Samsung's 990 PRO revision 1.0 reports writes with Intelligent TurboWrite active and limits that condition to a particular transfer size. The cited revision does not supply an after-cache write-rate figure. Do not turn its advertised rate into an estimate for an arbitrarily long copy. Firmware, host configuration and workload also matter. [2]
A NAND write buffer and DRAM are different resources. Samsung's historical 860 QVO paper describes a variable SLC-mode NAND buffer within a QLC drive; its capacity differs across the listed products. The 990 PRO datasheet separately lists LPDDR4 DRAM. Neither the presence of DRAM nor a NAND cache establishes the other resource's size or the device's power-loss guarantees. Consult the SLC-cache and mapping-cache explanations for their distinct roles. [3] [2]
For a long write comparison, record capacity, firmware, free space, preparation, transfer size, read/write mix, outstanding requests and temperature. Separate the initial burst from later behavior. SNIA specifies preparation and cache settings for comparative device tests; its client and enterprise settings differ. Cache exhaustion alone is not proof that the workload has reached steady state. [1]
Read endurance together with the warranty conditions. The cited 990 PRO revision lists 600 TBW for its 1 TB version and 1,200 TBW for its 2 TB version, with coverage limited by five years or TBW, whichever is reached first. Its JESD218 statement applies to those documented tests; it is not evidence that every retail SSD follows the same protocol. Treat the limit as a stated product condition, not a calendar for failure. [2]
Persistence is a separate question from speed. Linux documents that a volatile write-back cache can acknowledge a request before it reaches nonvolatile storage. A cache flush covers earlier completed writes; FUA requires persistence before completing the associated write. These are interface semantics when correctly propagated and honored throughout the storage path, not proof of emergency-power hardware in a named SSD. Do not infer that every consumer drive loses completed synchronized writes, or that every enterprise drive protects all in-flight data. [4]
Fault injection adds evidence that a product label cannot supply. Zheng and colleagues tested 15 SSDs from five vendors in FAST 2013, including devices labelled for enterprise use. Their raw-device workload used O_SYNC and O_DIRECT, with cache-flush issuance checked; 13 devices exhibited at least one failure behavior. This historical, selected sample is not a present-day consumer-drive failure probability. Repeated power cuts on a device are not independent samples of new devices. The existing power-fault analysis separates this report from its expanded journal version. [5]
Workload checks
Compare the actual workload and required persistence behavior. A client or enterprise label does not replace the model's specifications.
Questions to resolve before using a client SSD in a sustained or durability-sensitive workload
- Long writes
- Evidence to checkTransfer size and cache-active conditions. [2]
- Insufficient evidenceA peak MB/s figure alone.
- Repeatable performance
- Evidence to checkPreparation and reported cache settings. [1]
- Insufficient evidenceA fixed warm-up time alone.
- Write allowance
- Evidence to checkCapacity-specific TBW and warranty terms. [2]
- Insufficient evidenceThe consumer label.
- Persistent completion
- Evidence to checkDocumented flush/FUA behavior of the path. [4]
- Insufficient evidenceA fast write acknowledgement.
Uncertainty notes
- Source review, not a benchmark or a power-cut experiment.
- The Samsung documents describe particular product generations; their values are examples, not current buying recommendations or limits for all client SSDs.
- No class-wide absence or presence of power-loss protection, dual ports or a particular NAND type is asserted.
Sources
- 01SNIA: Solid State Storage Performance Test Specification 2.0.2 (2020), sections 1.1, 1.5, 2.1.3, 2.1.7 and 3.7. · accessed 2026-10-19
- 02Samsung: 990 PRO datasheet, revision 1.0, page 3, DRAM and warranty entries, footnotes 3, 4 and 6. Historical 1 TB and 2 TB configurations. · accessed 2026-10-19
- 03Samsung: 860 QVO white paper (June 2019), page 4, Intelligent TurboWrite and Table 2. Product-specific variable NAND buffer. · accessed 2026-10-19
- 04Linux v6.12 documentation: Explicit volatile write back cache control, cache flush and FUA sections. · accessed 2026-10-19
- 05Zheng, Tucek, Qin and Lillibridge. Understanding the Robustness of SSDs under Power Fault, FAST 2013, pp. 271-284, sections 3-5 and Tables 3-4. · accessed 2026-10-19