Merge pull request #289602 from b-ahibbard/justin-docs

new volume workload docs

Author: Jill Grant

articles/azure-netapp-files/TOC.yml

@@ -109,6 +109,8 @@
       items:
         - name: General performance considerations for Azure NetApp Files
           href: azure-netapp-files-performance-considerations.md  
+        - name: Understand workload types
+          href: workload-types.md
         - name: Linux direct I/O best practices
           href: performance-linux-direct-io.md
         - name: Linux filesystem cache best practices
@@ -133,6 +135,8 @@
       items:
       - name: Performance benchmark test recommendations for Azure NetApp Files
         href: azure-netapp-files-performance-metrics-volumes.md 
+      - name: Testing methodology
+        href: testing-methodology.md
       - name: Regular volume performance benchmarks for Linux
         href: performance-benchmarks-linux.md
       - name: Large volume performance benchmarks for Linux

articles/azure-netapp-files/azure-netapp-files-performance-metrics-volumes.md

@@ -5,7 +5,7 @@ author: b-hchen
 ms.author: anfdocs
 ms.service: azure-netapp-files
 ms.topic: conceptual
-ms.date: 05/08/2023
+ms.date: 10/31/2024
 ---
 # Performance benchmark test recommendations for Azure NetApp Files
 
@@ -16,9 +16,9 @@ This article provides benchmark testing recommendations for volume performance a
 To understand the performance characteristics of an Azure NetApp Files volume, you can use the open-source tool [FIO](https://github.com/axboe/fio) to run a series of benchmarks to simulate various workloads. FIO can be installed on both Linux and Windows-based operating systems.  It is an excellent tool to get a quick snapshot of both IOPS and throughput for a volume.
 
 > [!IMPORTANT]
-> Azure NetApp Files does *not* recommend using the `dd` utility as a baseline benchmarking tool. You should use an actual application workload, workload simulation, and benchmarking and analyzing tools (for example, Oracle AWR with Oracle, or the IBM equivalent for DB2) to establish and analyze optimal infrastructure performance. Tools such as FIO, vdbench, and iometer have their places in determining virtual machines to storage limits, matching the parameters of the test to the actual application workload mixtures for most useful results. However, it is always best to test with the real-world application. 
+> Azure NetApp Files does *not* recommend using the `dd` utility as a baseline benchmarking tool. You should use an actual application workload, workload simulation, and benchmarking and analyzing tools (for example, Oracle AWR with Oracle, or the IBM equivalent for Db2) to establish and analyze optimal infrastructure performance. Tools such as FIO, vdbench, and iometer have their places in determining virtual machines to storage limits, matching the parameters of the test to the actual application workload mixtures for most useful results. However, it is always best to test with the real-world application. 
  
-### VM instance sizing
+### Virtual machine (VM) instance sizing
 
 For best results, ensure that you are using a virtual machine (VM) instance that is appropriately sized to perform the tests. The following examples use a Standard_D32s_v3 instance. For more information about VM instance sizes, see [Sizes for Windows virtual machines in Azure](/azure/virtual-machines/sizes?toc=%2fazure%2fvirtual-network%2ftoc.json) for Windows-based VMs, and [Sizes for Linux virtual machines in Azure](/azure/virtual-machines/sizes?toc=%2fazure%2fvirtual-machines%2flinux%2ftoc.json) for Linux-based VMs.
 
@@ -48,50 +48,9 @@ Follow the Getting started section in the SSB README file to install for the pla
 
 ### FIO 
 
-Flexible I/O Tester (FIO) is a free and open-source disk I/O tool used both for benchmark and stress/hardware verification. 
+Flexible I/O Tester (FIO) is a free and open-source disk I/O tool used both for benchmark and stress/hardware verification. FIO is available in binary format for both Linux and Windows. 
 
-FIO is available in binary format for both Linux and Windows. 
-
-#### Installation of FIO
-
-Follow the Binary Packages section in the [FIO README file](https://github.com/axboe/fio#readme) to install for the platform of your choice.
-
-#### FIO examples for IOPS 
-
-The FIO examples in this section use the following setup:
-* VM instance size: D32s_v3
-* Capacity pool service level and size: Premium / 50 TiB
-* Volume quota size: 48 TiB
-
-The following examples show the FIO random reads and writes.
-
-##### FIO: 8k block size 100% random reads
-
-`fio --name=8krandomreads --rw=randread --direct=1 --ioengine=libaio --bs=8k --numjobs=4 --iodepth=128 --size=4G --runtime=600 --group_reporting`
-
-##### FIO: 8k block size 100% random writes
-
-`fio --name=8krandomwrites --rw=randwrite --direct=1 --ioengine=libaio --bs=8k --numjobs=4 --iodepth=128  --size=4G --runtime=600 --group_reporting`
-
-##### Benchmark results
-
-For official benchmark results for how FIO performs in Azure NetApp Files, see [Azure NetApp Files performance benchmarks for Linux](performance-benchmarks-linux.md).
-
-#### FIO examples for bandwidth
-
-The examples in this section show the FIO sequential reads and writes.
-
-##### FIO: 64k block size 100% sequential reads
-
-`fio --name=64kseqreads --rw=read --direct=1 --ioengine=libaio --bs=64k --numjobs=4 --iodepth=128  --size=4G --runtime=600 --group_reporting`
-
-##### FIO: 64k block size 100% sequential writes
-
-`fio --name=64kseqwrites --rw=write --direct=1 --ioengine=libaio --bs=64k --numjobs=4 --iodepth=128  --size=4G --runtime=600 --group_reporting`
-
-##### Benchmark results
-
-For official benchmark results for how FIO performs in Azure NetApp Files, see [Azure NetApp Files performance benchmarks for Linux](performance-benchmarks-linux.md).
+For more information, see [Understand Azure NetApp Files testing methodology](testing-methodology.md).
 
 ## Volume metrics
 
@@ -122,10 +81,11 @@ You can access Azure NetApp Files counters by using REST API calls. See [Support
 The following example shows a GET URL for viewing logical volume size:
 
 `#get ANF volume usage`  
-`curl -X GET -H "Authorization: Bearer TOKENGOESHERE" -H "Content-Type: application/json" https://management.azure.com/subscriptions/SUBIDGOESHERE/resourceGroups/RESOURCEGROUPGOESHERE/providers/Microsoft.NetApp/netAppAccounts/ANFACCOUNTGOESHERE/capacityPools/ANFPOOLGOESHERE/Volumes/ANFVOLUMEGOESHERE/providers/microsoft.insights/metrics?api-version=2018-01-01&metricnames=VolumeLogicalSize`
+`curl -X GET -H "Authorization: Bearer TOKENGOESHERE" -H "Content-Type: application/json" https://management.azure.com/subscriptions/<subscritionID>/resourceGroups/<resourceGroup>/providers/Microsoft.NetApp/netAppAccounts/<AzureNetAppFilesAccount>/capacityPools/<CapacityPool>/Volumes/<volume>/providers/microsoft.insights/metrics?api-version=2018-01-01&metricnames=VolumeLogicalSize`
 
 
 ## Next steps
 
 - [Service levels for Azure NetApp Files](azure-netapp-files-service-levels.md)
 - [Performance benchmarks for Linux](performance-benchmarks-linux.md)
+- [Understand Azure NetApp Files testing methodology](testing-methodology.md)

articles/azure-netapp-files/large-volumes.md

@@ -55,10 +55,11 @@ Large volumes allow workloads to extend beyond the current limitations of regula
 | Volume type | Primary use cases | 
 | - | -- |
 | Regular volumes | <ul><li>General file shares</li><li>SAP HANA and databases (Oracle, SQL Server, Db2, and others)</li><li>VDI/Azure VMware Service</li><li>Capacities less than 50 TiB</li></ul> |
-| Large volumes | <ul><li>General file shares</li><li>High file count or high metadata workloads (such as electronic design automation, software development, FSI)</li><li>High capacity workloads (such as AI/ML/LLP, oil & gas, media, healthcare images, backup, and archives)</li><li>Large-scale workloads (many client connections such as FSLogix profiles)</li><li>High performance workloads</li><li>Capacity quotas between 50 TiB and 1 PiB</li></ul> |
+| Large volumes | <ul><li>General file shares</li><li>High file count or high metadata workloads (such as electronic design automation, software development, financial services)</li><li>High capacity workloads (such as AI/ML/LLP, oil & gas, media, healthcare images, backup, and archives)</li><li>Large-scale workloads (many client connections such as FSLogix profiles)</li><li>High performance workloads</li><li>Capacity quotas between 50 TiB and 1 PiB</li></ul> |
 
 ## More information
 
 * [Requirements and considerations for large volumes](large-volumes-requirements-considerations.md)
 * [Storage hierarchy of Azure NetApp Files](azure-netapp-files-understand-storage-hierarchy.md)
 * [Resource limits for Azure NetApp Files](azure-netapp-files-resource-limits.md)
+* [Understand workload types in Azure NetApp Files](workload-types.md)