You can change the caching policy for a volume that resides on Flash Pool aggregates by using the -caching-policy parameter in the volume create command. When you create a volume on a Flash Pool aggregate, by default, the auto caching policy is assigned to the volume.
In most cases, the default caching policy is preferable. The caching policy for a volume should be changed only if a different policy provides better performance.
You can set the caching policies for a volume when you create a volume on the Flash Pool aggregate. You can modify the caching policy by using the volume modify command. The caching policies can also be moved between a Flash Pool aggregate and non-Flash Pool aggregate.
|Policy Name||Description||Read caching policy||Write caching policy||Privilege|
|auto||Read caches all metadata blocks and randomly read user data blocks and write caches all randomly overwritten user data blocks.||random_read||random-write||admin|
|none||Does not cache any user data or metadata blocks.||none||none||admin|
|random_read||Read caches all metadata blocks and randomly read user data blocks.||random_read||none||advanced|
|noread-random_write||Write caches all randomly overwritten user data blocks.||none||random-write||advanced|
|meta||Read caches only metadata blocks.||meta||none||advanced|
|meta-random_write||Read caches all metadata blocks and write caches all randomly overwritten user data blocks.||meta||random-write||advanced|
|random_read_write||Read caches all metadata, randomly read, and randomly written user data blocks.||random_read_write||none||advanced|
|random_read_write-random-write||Read caches all metadata, randomly read, and randomly written user data blocks. It also write caches randomly overwritten user data blocks.||random_read_write||random-write||advanced|