Deduplication ratio
Deduplication ratio compares bytes required without duplicate sharing with bytes required after duplicate sharing for the same stated population and accounting scope.
Scope: This ratio isolates deduplication rather than crediting compression or unwritten thin-provisioned space. Declare which stored versions, matching domain and overhead are included. SNIA distinguishes deduplication-only reduction from other space-saving effects. [1]
Payload convention: For exact matching with one stored copy per distinct identity, divide all occurrence bytes by unique payload bytes. For equal-length chunks, the occurrence-count ratio gives the same result; otherwise calculate from byte totals rather than assuming count ratios are equivalent. References, indexes, replicas and allocation padding are outside this payload-only calculation; include them separately for an all-in footprint.
Recipe cost: A reference per occurrence grows with logical content even when unique payload stays fixed. Recipe compression changes that cost. [3]
Selected objects: A reported deduplication ratio may cover only deduplication-eligible objects. That selection is not automatically the compressible-data population used by a reported compression ratio. [2]
Stage boundary: Let L be all occurrence bytes, U unique bytes before compression, and C their compressed bytes. For positive denominators, (L / U) * (U / C) = L / C. This cancellation requires the same U, time and accounting boundary; separately reported dashboard ratios do not establish those conditions.
Limits: A zero denominator does not provide a finite sizing ratio. The ratio alone establishes neither restore locality nor the additional bytes freed by deleting one retained version. Shared content can remain referenced by another version.
Relations
- related
- Data-reduction ratio, Data deduplication, Compression ratio, Content-based sampling (deduplication)
Citations
- SNIA Dictionary: compression ratio and data deduplication ratio, generated 17 November 2026
- Broadcom KB 315553: vSAN ESA 9.1 space-efficiency counter populations
- Meister, Brinkmann and Suss, File Recipe Compression in Data Deduplication Systems, FAST 2013, sections 1-3
Sources & caveats
- The L/U and U/C example is dimensional accounting for a stated deduplication-then-compression model, not a claim about every product's processing order.
- No measured array result, deduplication benchmark or capacity guarantee is implied.
- The selected-population example follows Broadcom's vSAN ESA 9.1 counter definitions, not a universal convention. [2]