A storage container option that reduces the physical space data takes up, either inline or post-process, for which Nutanix advises a 60-minute delay. High metadata usage turns it off automatically and raises an alert.
Read more: Nutanix docs
In the Ultra Transcenders books
Each book explains Compression in context, with comparison tables and the common traps.
Terms in this definition
- Storage container
Raw capacity on a vVols-capable array, presented through its VASA provider and shown in vCenter as a vVols datastore.
- Physical
Describes the concrete, real-world parts that put a logical architecture into effect.
- Metadata
Describes data rather than being the data itself, for instance how a file is laid out or what rows each chunk contains, so tools can read things efficiently.
- total_tokens
The usage field that sums prompt_tokens and completion_tokens, for example 37 + 86 = 123. Billing applies to both kinds of token.
Related terms
- Custom column
Created in Power Query by writing a formula in M. Guidance on reducing model size recommends it over adding the equivalent column in DAX, because compression tends to be better and refresh times aren't extended.
- Data Reduction Ratio
Shows in Prism how much space erasure coding, compression and deduplication save between them. Thin provisioning and cloning are added only in the Overall Efficiency number.
- Default storage policy
Sets compression and replication factor, leaving everything else to the cluster's storage settings, and offers no encryption. Prism Central has generated it since pc.2024.1, with full support on AOS 6.8 onwards.
- LZ4
The compression algorithm used by the Optimal level, which is recommended because it balances ratio against speed and puts the least CPU load on the proxy.
- Nutanix storage container
Carved logically from a storage pool, it contains vDisks and controls replication factor, erasure coding, deduplication and compression. Hyper-V mounts it as an SMB share; ESXi mounts it as an NFS datastore.
- Object space reservation
Deduplication and compression savings become ineffective once an object is thick provisioned through this vSAN storage policy rule, which reserves part of an object's logical size when it is created: none (thin, the default), 25, 50 or 75 per cent, or all of it (thick).
- Post-process compression
Compression on a storage container that happens some time after the write, with 60 minutes the suggested delay. The inline kind, by contrast, acts during the write.
- storage policy
Uses categories in Prism Central to set QoS, compression, encryption and replication factor for volume groups and VMs, taking precedence over what the container specifies.