Understanding workloads supported by StrictSync and Sync policies

StrictSync and Sync policies support all LUN based applications with FCP and iSCSI protocols, as well as NFSv3 protocol for enterprise applications such as databases, VMWare, and so on.

For a Sync policy, you need to consider a few important aspects while selecting the NFSv3 workloads. The amount of data read or write operations by workloads is not a consideration, as Sync policy can handle high read or write IO workloads. However, workloads that have excessive file creation, directory creation, file permission changes, or directory permission changes may not be suitable (these are referred to as high meta-data workloads). A typical example for high meta-data workloads are DevOps workloads that create multiple test files, run automation, and deletes the files. Another example is parallel build workloads that generate multiple temporary files during compilation. The impact of a high rate of write metadata activity is, it can cause synchronization between mirrors to temporarily break which stalls the write IO from the client.

For information about best practices and sizing of StrictSync policy and Sync policy , see NetApp ONTAP Resources page.