large volume throughput limits

Author: b-ahibbard

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

@@ -6,7 +6,7 @@ author: b-ahibbard
 ms.service: azure-netapp-files
 ms.custom: references_regions
 ms.topic: conceptual
-ms.date: 02/25/2025
+ms.date: 03/10/2025
 ms.author: anfdocs
 ---
 # Requirements and considerations for large volumes
@@ -24,7 +24,7 @@ The following requirements and considerations apply to large volumes. For perfor
 * Large volumes are currently not supported with Azure NetApp Files backup.
 * You can't create a large volume with application volume groups.
 * Currently, large volumes aren't suited for database (HANA, Oracle, SQL Server, etc.) data and log volumes. For database workloads requiring more than a single volume’s throughput limit, consider deploying multiple regular volumes. To optimize multiple volume deployments for databases, use [application volume groups](application-volume-group-concept.md).
-* Throughput ceilings for the three performance tiers (Standard, Premium, and Ultra) of large volumes are based on the existing 100-TiB maximum capacity targets. You're able to grow to 1 PiB with the throughput ceiling per the following table:  
+* Throughput ceilings for the three performance tiers (Standard, Premium, and Ultra) of large volumes are based on the existing 100-TiB maximum capacity targets. You're able to grow to one PiB with the throughput ceiling per the following table:  
 
     <table><thead>
       <tr>

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

@@ -21,15 +21,15 @@ All resources in Azure NetApp files have [limits](azure-netapp-files-resource-li
 | - | - | 
 | Capacity | <ul><li>50 GiB minimum</li><li>100 TiB maximum</li></ul> |
 | File count | 2,147,483,632 |
-| Performance | <ul><li>Standard: 1,600</li><li>Premium: 1,600</li><li>Ultra: 4,500</li></ul> |
+| Performance (MiB/s) | <ul><li>Standard: 1,600</li><li>Premium: 6,400</li><li>Ultra: 12,800</li></ul> |
 
 Large volumes have the following limits: 
 
 | Limit type | Values | 
 | - | - | 
 | Capacity | <ul><li>50 TiB minimum</li><li>1 PiB maximum (or [2 PiB by special request](azure-netapp-files-resource-limits.md#request-limit-increase))</li></ul> |
 | File count | 15,938,355,048 |
-| Performance | <ul><li>Standard: 1,600</li><li>Premium: 6,400</li><li>Ultra: 12,800</li></ul> |
+| Performance | The large volume performance limit is 12,800 MiB/s on all service levels. |
 
 
 ## Large volumes effect on performance 

articles/azure-netapp-files/performance-benchmarks-linux.md

@@ -139,7 +139,7 @@ The following tests show a high throughput benchmark using both 64-KiB and 256-K
 
 In this benchmark, FIO ran using looping logic that more aggressively populated the cache, so an indeterminate amount of caching influenced the results. This results in slightly better overall performance numbers than tests run without caching.  
 
-In the graph below, testing shows that an Azure NetApp Files regular volume can handle between approximately 4,500MiB/s pure sequential 64-KiB reads and approximately 1,600MiB/s pure sequential 64-KiB writes. The read-write mix for the workload was adjusted by 10% for each run.  
+In the graph below, testing shows that an Azure NetApp Files regular volume can handle between approximately 4,500MiB/s pure sequential 64-KiB reads and approximately 1,600 MiB/s pure sequential 64-KiB writes. The read-write mix for the workload was adjusted by 10% for each run.  
 
 :::image type="content" source="./media/performance-benchmarks-linux/64K-sequential-read-write.png" alt-text="Diagram of 64-KiB benchmark tests with sequential I/O and caching included." lightbox="./media/performance-benchmarks-linux/64K-sequential-read-write.png":::
 

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

@@ -13,7 +13,7 @@ ms.workload: storage
 ms.tgt_pltfrm: na
 ms.custom: linux-related-content
 ms.topic: conceptual
-ms.date: 10/25/2024
+ms.date: 03/10/2025
 ms.author: anfdocs
 ---
 # Azure NetApp Files large volume performance benchmarks for Linux
@@ -22,13 +22,7 @@ This article describes the tested performance capabilities of a single [Azure Ne
 
 ## Testing summary 
 
-* The Azure NetApp Files large volumes feature offers three service levels, each with throughput limits. The service levels can be scaled up or down nondisruptively as your performance needs change.  
-
-    * Ultra service level: 12,800 MiB/s
-    * Premium service level: 6,400 MiB/s
-    * Standard service level: 1,600 MiB/s
-
-    The Ultra service level was used in these tests. 
+* Azure NetApp Files offers three services levels. All three service levels support large volumes. The service levels can be scaled up or down nondisruptively. Although the throughput levels differ on _regular_ volumes, the large volume performance limit is 12,800 MiB/s on all service levels. The Ultra service level was used in these tests. 
 
 * Sequential writes: 100% sequential writes maxed out at ~8,500 MiB/second in these benchmarks. (A single large volume’s maximum throughput is capped at 12,800 MiB/second by the service, so more potential throughput is possible.)
 * Sequential reads: 100% sequential reads maxed out at ~12,761 MiB/second in these benchmarks. (A single large volume's throughput is capped at 12,800 MiB/second. This result is near the maximum achievable throughput at this time.)