Swift Object heatmap data tiering
Swift Object heatmap data tiering policies can be applied to data that is frequently accessed.
For more information about file access temperature, see File heat: Tracking file access temperature.
With the Swift Object heatmap data tiering policies,
frequently accessed Swift Objects are stored in
higher-performing storage pools such as the SSD-based pool. The policy also stores Swift Objects that are not accessed frequently in slower
disk-based storage pools.
Note: Data that is not required for regular access is moved from slower
disk-based storage pools to tapes.
The Swift Object heatmap policy
The Swift Object heatmap policy can be applied to Swift Object data files in the file system.
The policy manages the placement of Swift Objects in the gold, silver, and system pools. The policy also specifies the maximum threshold so that the capacity in the storage tiers is not over-utilized.
Enabling heatmap tracking
Enable heatmap tracking on the IBM
Storage Scale file
system by running the following
command:
mmchconfig fileheatperiodminutes=1440,fileheatlosspercent=10
mmchconfig: Command successfully completed
mmchconfig: Propagating the cluster configuration data to all
affected nodes. This is an asynchronous process.