Skip to content

Commit 8437944

Browse files
committed
s3
1 parent acfb5f3 commit 8437944

File tree

1 file changed

+10
-2
lines changed

1 file changed

+10
-2
lines changed

articles/azure-netapp-files/performance-benchmarks-azure-vmware-solution.md

Lines changed: 10 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: azure-netapp-files
55
author: b-hchen
66
ms.service: azure-netapp-files
77
ms.topic: conceptual
8-
ms.date: 02/07/2024
8+
ms.date: 12/02/2024
99
ms.author: anfdocs
1010
---
1111
# Azure NetApp Files datastore performance benchmarks for Azure VMware Solution
@@ -21,7 +21,15 @@ The following `read:write` I/O ratios were tested for each scenario: `100:0, 75:
2121

2222
Benchmarks documented in this article were performed with sufficient volume throughput to prevent soft limits from affecting performance. Benchmarks can be achieved with Azure NetApp Files Premium and Ultra service levels, and in some cases with Standard service level. For more information on volume throughput, see [Performance considerations for Azure NetApp Files](azure-netapp-files-performance-considerations.md).
2323

24-
Refer to the [Azure NetApp Files datastore for Azure VMware Solution TCO Estimator](https://aka.ms/anfavscalc) to understand the sizing and associated cost benefits of Azure NetApp Files datastores.
24+
Consult the [Azure NetApp Files datastore for Azure VMware Solution TCO Estimator](https://aka.ms/anfavscalc) to understand the sizing and associated cost benefits of Azure NetApp Files datastores.
25+
26+
## Latency
27+
28+
Traffic latency from AVS to Azure NetApp Files datastores varies from submillisecond (for environments under minimal load) up to 2-3 milliseconds (for environments under medium to heavy load). The latency is potentially higher for environments that attempt to push beyond the throughput limits of various components. Latency and throughput may vary depending on several factors, including I/O size, read/write ratios, competing network traffic, and so on.
29+
30+
31+
32+
<!-- -->
2533

2634
## Environment details
2735

0 commit comments

Comments
 (0)