APEX File Storage for Microsoft Azure supports Ddv5-series, Ddsv5-series, Edv5-series, and Edsv5-series VM types with a minimum of 32 vCPUs. Different Azure VM sizes provide different compute, memory, storage, and network capabilities. Choose a VM size based on the requirements of your workload. Here are some guidelines to consider:
- Network bandwidth: In an Azure cloud environment, larger virtual machines receive more bandwidth compared to smaller ones. The allocation of network bandwidth to each virtual machine is measured based on egress traffic across all network interfaces attached to a virtual machine. Ingress traffic is not directly metered or restricted. For example, a Standard_D48ds_v5 OneFS node has max 24,000 Mbps network bandwidth, which is shared by both node’s external and internal interfaces. For details on the maximum network bandwidth of each VM size, refer to Azure documentation Ddv5 and Ddsv5-series and Edv5 and Edsv5-series.
- Max uncached disk throughput: the default storage maximum throughput limit that the virtual machine can handle. Refer to Azure documentation for more details.
- Max burst uncached disk throughput: leverages the virtual machine-level bursting to achieve higher storage throughput than max uncached disk throughput. When a deployment is planned, it is recommended to
see Appendix C: recommended data disk configuration details for optimal performance for data disks configuration per node. - Virtual machine-level bursting: OneFS cluster performance can benefit from the Azure VM burst capability to temporarily increase the cluster performance beyond their baseline. Refer to Azure bursting documentation for more details.
- Disk encryption key management: Azure managed disks typically use Azure Storage encryption, utilizing server-side encryption (SSE) to safeguard data and ensure compliance with security and organizational requirements. APEX File Storage supports both platform-managed keys and customer-managed keys.