update throughput values, examples, and storage hierarchy graphic

Author: b-ahibbard

articles/azure-netapp-files/azure-netapp-files-service-levels.md

@@ -5,7 +5,7 @@ services: azure-netapp-files
 author: b-hchen
 ms.service: azure-netapp-files
 ms.topic: conceptual
-ms.date: 01/24/2025
+ms.date: 03/10/2025
 ms.author: anfdocs
 ---
 # Service levels for Azure NetApp Files
@@ -71,8 +71,7 @@ The following diagram illustrates the scenarios for the SAP HANA volumes but wit
 
 :::image type="content" source="./media/azure-netapp-files-service-levels/flexible-service-sap-hana-examples.png" alt-text="Diagram of Flexible service level throughput with SAP HANA volumes." lightbox="./media/azure-netapp-files-service-levels/flexible-service-sap-hana-examples.png":::
 
-
-The example extends to the Flexible service as well. A Flexible service level capacity pool can be used to create the following volumes. Each volume provides the individual size and throughput to meet your application requirements:
+The example extends to the Flexible service level as well. A Flexible service level capacity pool can be used to create the following volumes. Each volume provides the individual size and throughput to meet your application requirements:
 
 - SAP HANA data volume: Size 4 TiB with up to 704 MiB/s
 - SAP HANA log volume: Size 0.5 TiB with up to 256 MiB/s
@@ -87,10 +86,10 @@ As illustrated in the diagram, the SAP HANA backup volume received the 128MiB/s
 | - | - | -- |
 | 1 | 128 | 5 * 128 * 1 = 640 |
 | 2 | 128 | 5 * 128 * 2 = 1,280 |
-| 5 | 128 | 5 * 128 * 5 = 3,200 |
 | 10 | 128 | 5 * 128 * 10 = 6,400 |
 | 50 | 128 | 5 * 128 * 50 = 32,000 |
 | 100 | 128 | 5 * 128 * 100 = 64,000 |
+| 1,024 | 128 | 5 * 128 * 1,024 = 655,360 |
 
 >[!NOTE]
 >A Flexible capacity pool with 128 MiB/s throughput assigned to it is only charged for the allocated capacity.

articles/azure-netapp-files/azure-netapp-files-set-up-capacity-pool.md

@@ -5,7 +5,7 @@ services: azure-netapp-files
 author: b-hchen
 ms.service: azure-netapp-files
 ms.topic: how-to
-ms.date: 02/28/2025
+ms.date: 03/10/2025
 ms.author: anfdocs
 ms.custom: references_regions
 ---

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
@@ -20,17 +20,17 @@ The following requirements and considerations apply to large volumes. For perfor
 * A regular volume can’t be converted to a large volume.
 * You must create a large volume at a size of 50 TiB or larger. The maximum size of a large volume is 1,024 TiB, though 2-PiB large volumes are available on request depending on regional dedicated capacity availability. To request 2-PiB large volumes, contact your account team. 
 * You can't resize a large volume to less than 50 TiB.
-    A large volume cannot be resized to more than 30% of its lowest provisioned size. This limit is adjustable via [a support request](azure-netapp-files-resource-limits.md#resource-limits). When requesting the resize, specify the exact size desired size in TiB. 
+    A large volume cannot be resized to more than 30% of its lowest provisioned size. This limit is adjustable via [a support request](azure-netapp-files-resource-limits.md#resource-limits). When requesting the resize, specify the desired size in TiB. 
 * 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 all three performance tiers (Standard, Premium, and Ultra) of large volumes is 12,800 MiB/s. You're able to grow to 1 PiB with the throughput ceiling per the following table:  
 
     <table><thead>
       <tr>
         <th></th>
         <th colspan="2">Capacity</th>
-        <th colspan="2">Linear performance scaling per TiB up to maximum allowed capacity tier throughput (large volume) </th>
+        <th colspan="2">Linear performance scaling per TiB up to maximum 12,800 MiB/s </th>
       </tr></thead>
     <tbody>
       <tr>

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

@@ -6,7 +6,7 @@ author: b-ahibbard
 ms.service: azure-netapp-files
 ms.custom: references_regions
 ms.topic: conceptual
-ms.date: 10/29/2024
+ms.date: 03/10/2025
 ms.author: anfdocs
 ---
 # Understand large volumes in Azure NetApp Files 
@@ -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: 1,600</li><li>Ultra: 4,500</li><li>Flexible: 4,500</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 regardless of service level. |
 
 
 ## Large volumes effect on performance 
@@ -53,7 +53,7 @@ Regular volumes can handle most workloads. Once capacity, file count, performanc
 Large volumes allow workloads to extend beyond the current limitations of regular volumes. The following table shows some examples of use cases for each volume type.
 
 | 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, 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> |