Azure Performance Test: Azure NetApp Files Benchmarks

Putting Azure NetApp Files to the test. These benchmarks
show the performance that Azure NetApp Files delivers

image-placeholder

SectionHeading

  • Lorem Ipsum is simply dummy text of the printing
  • Typesetting industry.
  • Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown
  • Printer took a galley of type and scrambled it to make a type specimen book.
  • Linux
  • Oracle

Linux

Linux Workload - IOPS

Our Azure performance test indicates that the maximum I/O that a customer can drive from multiple clients, against a single Azure NetApp Files volume is around ~317K 8KiB IOPS.

azure-diagram-01

Linux Workload – Throughput

Our sequential test was done using the exact same tests and procedures. In this case the maximum amount of I/O that can be driven to a single volume is right around ~4,5GiBps reads for 64KiB.

azure-diagram-02


Up to ~319,000 IOPS at 1.5ms latency

Our Azure performance tests show that Azure NetApp Files performs at minimal latency regardless of whether the Azure virtual machines are in the same Azure Data Center or Campus as the ANF storage system or not (i.e adjacent or non-adjacnet). An Azure NetApp Files volume is able to generate ~319,000 IOPS at only 1.5ms latency for adjacent virtual machines and ~290,000 IOPS below the 2ms latency mark for non-adjacent virtual machines.

Read this blog for more information on the performance customers can get with Azure NetApp Files.

azure-diagram-03

Oracle

Oracle IOPS with Azure NetApp Files

The graph shows Oracle database performance when using Azure NetApp Files on the Oracle SLOB benchmark. Running a mixed read/write Oracle workload in a single Standard D64s_v3 Linux VM instance is able to drive 71,000 file system IOPS at sub-0.5 msec latency in a single NFS volume, and up to 218,000 IOPS while still below 2.5 msec. Adding a 2nd Azure NetApp Files data volume enables scaling performance even higher to 310,000 IOPS and beyond while latency remains well below 2 msec.

azure-diagram-04 (1)