NCP-MCI-6.10 · Question #110
An administrator received a request to create a new storage container for persistent desktops. Which storage optimization setting must the administrator set for the best possible capacity savings?
The correct answer is B. Inline compression with a delay of 0 minutes. For persistent virtual desktops, inline compression with a 0-minute delay provides the best storage capacity savings by compressing data as it is written with no deferral. This maximizes space savings on write-heavy, non-deduplication-friendly persistent desktop workloads.
Question
An administrator received a request to create a new storage container for persistent desktops. Which storage optimization setting must the administrator set for the best possible capacity savings?
Options
- AErasure Coding
- BInline compression with a delay of 0 minutes
- CInline Deduplication of Read Caches
- DPost Process Deduplication
How the community answered
(61 responses)- A5% (3)
- B74% (45)
- C13% (8)
- D8% (5)
Why each option
For persistent virtual desktops, inline compression with a 0-minute delay provides the best storage capacity savings by compressing data as it is written with no deferral. This maximizes space savings on write-heavy, non-deduplication-friendly persistent desktop workloads.
Erasure Coding reduces storage overhead by replacing replicas with parity stripes, but it is most beneficial at scale for cold data and adds latency overhead that is not ideal for active desktop workloads.
Inline compression with a delay of 0 minutes compresses data at write time before it is committed to storage, meaning every write is compressed immediately without waiting for a post-process pass. Persistent desktops generate unique, non-repetitive user data that responds well to compression but poorly to deduplication, making inline compression the most effective capacity-saving setting for this workload type.
Inline Deduplication of Read Caches targets duplicate blocks in the read cache tier and does not directly reduce persistent storage capacity for unique desktop data.
Post Process Deduplication scans data after it is written to find duplicates, but persistent desktop workloads contain largely unique user data with low deduplication ratios, making this setting ineffective for capacity savings.
Concept tested: Nutanix storage container inline compression for VDI
Source: https://portal.nutanix.com/page/documents/details?targetId=Web-Console-Guide:wc-storage-container-create-wc.html
Topics
Community Discussion
No community discussion yet for this question.