Industry Insights

1 DWPD Versus 3 DWPD: Reading the Write Budget When Two Capacity Ladders Do Not Line Up

작성: JH Semiconductorread intensive / mixed use / DWPD

The J750 and J770 capacity points do not map onto each other, so moving between them is never a like-for-like swap of endurance at constant capacity. DWPD is a relative scale: it has to be multiplied out into absolute daily terabytes before two tiers can be compared, and node raw capacity has to be reconciled against node daily write budget.

Two rulers whose graduations do not line up

The J750 is offered at 1.92/3.84/7.68/15.36 TB and the J770 at 1.6/3.2/6.4/12.8 TB. The two ladders differ by roughly 17% step for step, and no rung on one lands on a rung of the other. Moving between them is therefore never "same capacity, more endurance": it changes the capacity point, the per-drive write budget and the way a node is assembled, all at once. Every figure on both ladders is a product-definition/EVT planning value; model names were frozen on 2026-07-22 while capacity points themselves are managed through SKU and PN, so a technical discussion should name the SKU rather than only the series.

DWPD is a relative scale — multiply it out

The denominator of DWPD is nominal capacity, so the same DWPD number means very different write budgets at different capacity points. The J750 is defined at 1 DWPD over five years: the 3.84 TB rung permits 3.84 TB of writes per day. The J770 is defined at 3 DWPD: its neighbouring 3.2 TB rung permits 9.6 TB per day. The smaller capacity carries two and a half times the absolute write budget. Comparing the two lines starts by converting DWPD into terabytes per day; skip that and it is easy to reach the exactly inverted conclusion that the larger drive tolerates more writing.

Reconcile three quantities at node level

Per-drive capacity sets the granularity of a node. Take one 24-bay chassis: fully populated with 3.84 TB J750s it holds 92.16 TB raw and absorbs roughly 92 TB of writes per day; fully populated with 3.2 TB J770s it holds 76.8 TB raw and absorbs roughly 230 TB per day. The two land differently in replication or erasure-coding planning, and differ by nearly two and a half times in the write intensity they can sustain. The three quantities to reconcile together are node raw capacity, node daily write budget and the bay count the chassis provides. Quoting per-drive capacity without the write budget tends to surface as a problem only a year or two into deployment.

Workloads neither ladder should be forced onto

CORE 7 is positioned as the mainstream cost-oriented line for general-purpose servers, Ceph and virtualisation. Object storage, backup and archive belong instead to Q7 — J760Q and J760QD. AI checkpointing and very large capacity arrays map to Q9 — J960Q and J960QD. Metadata, journal and cache tiers, with their small high-frequency writes, belong to X7's J790X and J795X. Forcing CORE 7 onto these either loses on capacity cost or runs out of write budget, and switching ladders does not recover it.

Everything outside the difference is common baseline

Both models share the U.2/U.3 15mm form factor, a PCIe 4.0 x4 interface, NVMe 1.4+, a single-port design and 3D Enterprise TLC media. Sequential read of 7,400 MB/s, sequential write of 5,500 MB/s and 1,500 KIOPS 4KB random read are identical, as are MTBF of at least 2 million hours, UBER of no more than one sector per 10^18 bits and a five-year warranty. Only DWPD and 4KB random write (300 versus 600 KIOPS) are tiered. Selection should therefore converge on one checkable number: how many terabytes this node writes to disk per day, and which rung of which ladder that lands on.

키워드
read intensivemixed useDWPDcapacity ladderdaily write budgetnode planningCORE 7JH Semiconductor