Skip to content

Commit c915bba

Browse files
committed
coolness period recommendations for ANF with AVS
1 parent fd4442b commit c915bba

File tree

1 file changed

+21
-1
lines changed

1 file changed

+21
-1
lines changed

articles/azure-vmware/attach-azure-netapp-files-to-azure-vmware-solution-hosts.md

Lines changed: 21 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Attach Azure NetApp Files datastores to Azure VMware Solution hosts
33
description: Learn how to create Azure NetApp Files-based NFS datastores for Azure VMware Solution hosts.
44
ms.topic: how-to
55
ms.service: azure-vmware
6-
ms.date: 3/22/2024
6+
ms.date: 10/11/2024
77
ms.custom: "references_regions, engagement-fy23"
88
---
99

@@ -95,6 +95,26 @@ There are some important best practices to follow for optimal performance of NFS
9595

9696
For performance benchmarks that Azure NetApp Files datastores deliver for VMs on Azure VMware Solution, see [Azure NetApp Files datastore performance benchmarks for Azure VMware Solution](../azure-netapp-files/performance-benchmarks-azure-vmware-solution.md).
9797

98+
99+
### Considerations for Azure NetApp Files storage with cool access
100+
101+
When choosing to use Azure NetApp Files storage with cool access on datastores for AVS, consider the performance characteristics of your workloads. Cool access is best suited for applications and workloads that primarily involve sequential I/O operations or tolerate varying read latency. Workloads with high random I/O and latency sensitivity should avoid using cool access due to an increase in latency when reading data from the cool tier.
102+
103+
Also consider adjusting cool access settings for the workload to fit the expected access patterns. For more information, see [Performance considerations for Azure NetApp Files storage with cool access](../azure-netapp-files/performance-considerations-cool-access.md).
104+
105+
**Use cases where cool access is a good fit:**
106+
107+
- Virtual machine templates and ISO files
108+
- VMDKs with home directories (if not using Azure NetApp Files directly for this purpose)
109+
- VMDKs with content repositories
110+
- VMDKs with application data
111+
- VMDKs with archive and application-level backup data
112+
113+
**Use cases to not use cool access:**
114+
115+
- VMDKs containing production database files with high random I/O and latency sensitivity
116+
- VMDKs with operating system boot disks
117+
98118
## Attach an Azure NetApp Files volume to your private cloud
99119

100120
### [Portal](#tab/azure-portal)

0 commit comments

Comments
 (0)