Thanks for the reply! Your description of the purpose of workloads made things much clearer. I have also done a quick test with different workloads and found that most of the predefined workloads are indeed merely a "Tag", i.e. they do not result in any parametric/configuration differences in the created volume (all settings have default values).
There are, however, some exceptions as described in the following link. In fact, the descriptions in this link is what made me so confused in the first place.
The 4 workloads listed in the link do actually cause different volume/system settings to better optimize the performance in each use case:
●Microsoft® SQL Server™
●Microsoft® Exchange Server™
●Video Surveillance applications
●VMware ESXi ™(for volumes to be used with Virtual Machine File System)
In fact, the two Microsoft workloads and VMware ESXi will bring up their own unique volume creation GUI for defining specific volume combinations and settings. For Video Surveillance applications, there are no special volume creation GUI, but as far as I know, the resultant volumes have 'write cache mirroring' disable to improve data write performance.
I think Netapp could have elaborated more on that in their help documentation, and state more clearly the settings that were optimized in each case.
Please correct me if my understanding above is missing anything. Thanks!