Merge pull request #225934 from khdownie/kendownie020123

adding links to performance article

Author: prmerger-automator[bot]

articles/storage/files/storage-files-scale-targets.md

@@ -12,7 +12,7 @@ ms.subservice: files
 # Azure Files scalability and performance targets
 [Azure Files](storage-files-introduction.md) offers fully managed file shares in the cloud that are accessible via the SMB and NFS file system protocols. This article discusses the scalability and performance targets for Azure Files and Azure File Sync.
 
-The targets listed here might be affected by other variables in your deployment. For example, the performance of IO for a file might be impacted by your SMB client's behavior and by your available network bandwidth. You should test your usage pattern to determine whether the scalability and performance of Azure Files meet your requirements. You should also expect these limits will increase over time. 
+The targets listed here might be affected by other variables in your deployment. For example, the performance of I/O for a file might be impacted by your SMB client's behavior and by your available network bandwidth. You should test your usage pattern to determine whether the scalability and performance of Azure Files meet your requirements. You should also expect these limits will increase over time. 
 
 ## Applies to
 | File share type | SMB | NFS |
@@ -83,9 +83,9 @@ File scale targets apply to individual files stored in Azure file shares.
 | Maximum egress for a file | 60 MiB/sec | 300 MiB/sec (Up to 1 GiB/s with SMB Multichannel)<sup>2</sup> |
 | Maximum concurrent handles per file, directory, and share root<sup>3</sup> | 2,000 handles | 2,000 handles  |
 
-<sup>1 Applies to read and write IOs (typically smaller IO sizes less than or equal to 64 KiB). Metadata operations, other than reads and writes, may be lower.</sup>
+<sup>1 Applies to read and write I/Os (typically smaller I/O sizes less than or equal to 64 KiB). Metadata operations, other than reads and writes, may be lower.</sup>
 
-<sup>2 Subject to machine network limits, available bandwidth, IO sizes, queue depth, and other factors. For details see [SMB Multichannel performance](./storage-files-smb-multichannel-performance.md).</sup>
+<sup>2 Subject to machine network limits, available bandwidth, I/O sizes, queue depth, and other factors. For details see [SMB Multichannel performance](./storage-files-smb-multichannel-performance.md).</sup>
 
 <sup>3 Azure Files supports 2,000 open handles per share, and in practice can go higher. However, if an application keeps an open handle on the root of the share, the share root limit will be reached before the per-file or per-directory limit is reached.</sup>
 
@@ -176,5 +176,6 @@ As a general guide for your deployment, you should keep a few things in mind:
 - The object throughput is inversely proportional to the MiB per second throughput. For smaller files, you will experience higher throughput in terms of the number of objects processed per second, but lower MiB per second throughput. Conversely, for larger files, you will get fewer objects processed per second, but higher MiB per second throughput. The MiB per second throughput is limited by the Azure Files scale targets.
 
 ## See also
+- [Understand Azure Files performance](understand-performance.md)
 - [Planning for an Azure Files deployment](storage-files-planning.md)
 - [Planning for an Azure File Sync deployment](../file-sync/file-sync-planning.md)

articles/storage/files/storage-files-smb-multichannel-performance.md

@@ -131,11 +131,11 @@ The following tips may help you optimize your performance:
 - The initial test is usually a warm-up, discard its results and repeat the test.
 - If performance is limited by a single client and workload is still below provisioned share limits, higher performance can be achieved by spreading load over multiple clients.
 
-### The relationship between IOPS, throughput, and IO sizes
+### The relationship between IOPS, throughput, and I/O sizes
 
 **Throughput = IO size * IOPS**
 
-Higher IO sizes drive higher throughput and will have higher latencies, resulting in a lower number of net IOPS. Smaller IO sizes will drive higher IOPS but results in lower net throughput and latencies.
+Higher I/O sizes drive higher throughput and will have higher latencies, resulting in a lower number of net IOPS. Smaller I/O sizes will drive higher IOPS but will result in lower net throughput and latencies. To learn more, see [Understand Azure Files performance](understand-performance.md).
 
 ## Next steps
 - [Enable SMB Multichannel](files-smb-protocol.md#smb-multichannel)

articles/storage/files/storage-troubleshooting-files-performance.md

@@ -326,6 +326,7 @@ Depending on the exact compression method and unzip operation used, decompressio
 To learn more about configuring alerts in Azure Monitor, see [Overview of alerts in Microsoft Azure](../../azure-monitor/alerts/alerts-overview.md).
 
 ## See also
-- [Troubleshoot Azure Files in Windows](storage-troubleshoot-windows-file-connection-problems.md)  
+- [Troubleshoot Azure Files in Windows](storage-troubleshoot-windows-file-connection-problems.md)
 - [Troubleshoot Azure Files in Linux](storage-troubleshoot-linux-file-connection-problems.md)  
+- [Understand Azure Files performance](understand-performance.md)
 - [Azure Files FAQ](storage-files-faq.md)