Skip to content

Commit ffad5bf

Browse files
committed
av36 performance benchmarks
1 parent 7afb3d3 commit ffad5bf

File tree

7 files changed

+32
-19
lines changed

7 files changed

+32
-19
lines changed
64.7 KB
Loading
119 KB
Loading
Loading
158 KB
Loading
204 KB
Loading
238 KB
Loading

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

Lines changed: 32 additions & 19 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: 12/02/2024
8+
ms.date: 12/03/2024
99
ms.author: anfdocs
1010
---
1111
# Azure NetApp Files datastore performance benchmarks for Azure VMware Solution
@@ -38,7 +38,7 @@ Each AVS Host connects to each Azure NetApp Files datastore with a fixed number
3838
3939
Throughput for each individual host may be affected by the selected AVS SKU. The AV64 SKU has 100-Gigabit Ethernet (GbE) network interface cards (NICs). The other SKUs have 25 GbE NICs. Individual network flows (such as NFS mounts) may be limited by the 25 GbE NICs.
4040

41-
## Av 64 environment details
41+
## AV64 environment details
4242

4343
The results in this article were achieved using the following environment configuration:
4444

@@ -48,41 +48,54 @@ The results in this article were achieved using the following environment config
4848
* Workload generator: `fio` 3.35
4949

5050
>[!NOTE]
51-
> The AV64 tests focus only on the evaluation of a single ESXi host. Scaling out the number of ESXi hosts is discussed in the AV36 section.
51+
> The AV64 tests focus only on the evaluation of a single ESXi host. Scaling out the number of ESXi hosts is discussed in the [AV36 section](#av-36-environment-details).
5252
53-
## Next steps
53+
### One-to-multiple Azure NetApp Files datastores with a single AV64 host
5454

55-
- [Attach Azure NetApp Files datastores to Azure VMware Solution hosts: Performance best practices ](../azure-vmware/attach-azure-netapp-files-to-azure-vmware-solution-hosts.md#performance-best-practices)
55+
The following graphs compare the throughput of a single virtual machine on a single Azure NetApp Files datastore with the aggregated throughput of eight VMs, each on their own Azure NetApp Files datastores. Similar throughput can be achieved by a smaller number of VMs with additional VMDKs spread across the same number of datastores.
5656

57-
<!-- -->
57+
:::image type="content" source="./media/performance-benchmarks-azure-vmware-solution/one-to-multiple-datastores-diagram.png" alt-text="Diagram comparing one Azure NetApp File datastore set up to multiple datastores." lightbox="./media/performance-benchmarks-azure-vmware-solution/one-to-multiple-datastores-diagram.png":::
5858

59+
This graph compares throughput:
5960

61+
:::image type="content" source="./media/performance-benchmarks-azure-vmware-solution/total-throughput-64kb.png" alt-text="Charts comparing throughput on one and eight datastores." lightbox="./media/performance-benchmarks-azure-vmware-solution/total-throughput-64kb.png":::
6062

61-
## Latency
63+
This graph compares I/OPS:
6264

63-
Traffic latency from AVS to Azure NetApp Files datastores varies from sub-millisecond (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.
65+
:::image type="content" source="./media/performance-benchmarks-azure-vmware-solution/input-ouptut-one-eight.png" alt-text="Charts comparing I/OPS on one and eight datastores." lightbox="./media/performance-benchmarks-azure-vmware-solution/input-ouptut-one-eight.png":::
6466

65-
## One-to-multiple virtual machines running on a single AVS host and a single Azure NetApp Files datastore
67+
## AV36 environment details
6668

67-
In a single AVS host scenario, the AVS to Azure NetApp Files datastore I/O occurs over a single network flow. The following graphs compare the throughput and IOPs of a single virtual machine with the aggregated throughput and IOPs of four virtual machines. In the subsequent scenarios, the number of network flows increases as more hosts and datastores are added.
69+
These tests were conducted with an environment configuration using:
6870

71+
- Azure VMware Solution host size: AV36 running VMware ESXi version 7u3
72+
- Azure VMware Solution private cloud connectivity: UltraPerformance gateway with FastPath
73+
- Guest virtual machines: Ubuntu 21.04, 16 vCPU, 64 GB Memory
74+
- Workload generator: `fio`
6975

70-
## One-to-multiple Azure NetApp Files datastores with a single AVS host
76+
### One-to-multiple virtual machines running on a single AV36 host and a single Azure NetApp Files datastore
7177

72-
The following graphs compare the throughput of a single virtual machine on a single Azure NetApp Files datastore with the aggregated throughput of four Azure NetApp Files datastores. In both scenarios, each virtual machine has a VMDK on each Azure NetApp Files datastore.
78+
In a single AVS host scenario, the AVS to Azure NetApp Files datastore I/O occurs over a single network flow. These graphs compare the throughput and I/OPs of a single virtual machine with the aggregated throughput and I/OPS of four virtual machines. In the subsequent scenarios, the number of network flows increases as more hosts and datastores are added.
7379

74-
:::image type="content" source="./media/performance-benchmarks-azure-vmware-solution/performance-vmware-one-host-four-datastores.png" alt-text="Graphs comparing a single virtual machine on a single datastore with four datastores." lightbox="./media/performance-benchmarks-azure-vmware-solution/performance-vmware-one-host-four-datastores.png":::
80+
:::image type="content" source="./media/performance-benchmarks-azure-vmware-solution/throughput-one-to-multiple.png" alt-text="Diagram comparing one-to-multiple virtual machines running on a single AV36 host and a single Azure NetApp Files datastore." lightbox="./media/performance-benchmarks-azure-vmware-solution/throughput-one-to-multiple.png":::
7581

76-
The following graphs compare the IOPs of a single virtual machine on a single Azure NetApp Files datastore with the aggregated IOPs of eight Azure NetApp Files datastores. In both scenarios, each virtual machine has a VMDK on each Azure NetApp Files datastore.
82+
### One-to-multiple Azure NetApp Files datastores with a single AV36 host
7783

78-
:::image type="content" source="./media/performance-benchmarks-azure-vmware-solution/performance-vmware-one-host-eight-datastores.png" alt-text="Graphs comparing a single virtual machine on a single datastore with eight datastores." lightbox="./media/performance-benchmarks-azure-vmware-solution/performance-vmware-one-host-eight-datastores.png":::
84+
The following graphs compare the throughput of a single virtual machine on a single Azure NetApp Files datastore with the aggregated throughput of four Azure NetApp Files datastores. In both scenarios, each virtual machine has a VMDK on each Azure NetApp Files datastore.
7985

80-
## Scale-out Azure NetApp Files datastores with multiple AVS hosts
86+
:::image type="content" source="./media/performance-benchmarks-azure-vmware-solution/throughput-single-host.png" alt-text="Charts comparing throughput with a single AV36 host." lightbox="./media/performance-benchmarks-azure-vmware-solution/throughput-single-host.png":::
8187

82-
The following graph shows the aggregated throughput and IOPs of 16 virtual machines distributed across four AVS hosts. There are four virtual machines per AVS host, each on a different Azure NetApp Files datastore.
88+
The following graphs compare the I/OPS of a single virtual machine on a single Azure NetApp Files datastore with the aggregated I/OPS of eight Azure NetApp Files datastores. In both scenarios, each virtual machine has a VMDK on each Azure NetApp Files datastore.
8389

84-
Nearly identical results were achieved with a single virtual machine on each host with four VMDKs per virtual machine and each of those VMDKs on a separate datastore.
90+
:::image type="content" source="./media/performance-benchmarks-azure-vmware-solution/input-output-single-host.png" alt-text="Charts comparing I/OPS with a single AV36 host." lightbox="./media/performance-benchmarks-azure-vmware-solution/input-output-single-host.png":::
8591

86-
:::image type="content" source="./media/performance-benchmarks-azure-vmware-solution/performance-vmware-scale-out.png" alt-text="Graphs showing aggregated throughput and IOPs of 16 virtual machines distributed across four AVS hosts." lightbox="./media/performance-benchmarks-azure-vmware-solution/performance-vmware-scale-out.png":::
92+
### Scale-out Azure NetApp Files datastores with multiple AV36 hosts
8793

94+
The following graph shows the aggregated throughput and I/OPS of 16 virtual machines distributed across four AVS hosts. There are four virtual machines per AVS host, each on a different Azure NetApp Files datastore.
95+
Nearly identical results were achieved with a single virtual machine on each host with four VMDKs per virtual machine and each of those VMDKs on a separate datastore.
8896

97+
:::image type="content" source="./media/performance-benchmarks-azure-vmware-solution/performance-vmware-scale-out.png" alt-text="Graphs showing aggregated throughput and I/OPS of 16 virtual machines distributed across four AVS hosts." lightbox="./media/performance-benchmarks-azure-vmware-solution/performance-vmware-scale-out.png":::
98+
99+
## Next steps
100+
101+
- [Attach Azure NetApp Files datastores to Azure VMware Solution hosts: Performance best practices ](../azure-vmware/attach-azure-netapp-files-to-azure-vmware-solution-hosts.md#performance-best-practices)

0 commit comments

Comments
 (0)