Scalability and performance targets for premium page blob storage accounts

This reference details scalability and performance targets for Azure Storage. The scalability and performance targets listed here are high-end targets, but are achievable. In all cases, the request rate and bandwidth achieved by your storage account depends upon the size of objects stored, the access patterns utilized, and the type of workload your application performs.

Make sure to test your service to determine whether its performance meets your requirements. If possible, avoid sudden spikes in the rate of traffic and ensure that traffic is well-distributed across partitions.

When your application reaches the limit of what a partition can handle for your workload, Azure Storage begins to return error code 503 (Server Busy) or error code 500 (Operation Timeout) responses. If 503 errors are occurring, consider modifying your application to use an exponential backoff policy for retries. The exponential backoff allows the load on the partition to decrease, and to ease out spikes in traffic to that partition.

Scale targets for premium page blob accounts

A premium-performance page blob storage account is optimized for read/write operations. This type of storage account backs an unmanaged disk for an Azure virtual machine.

Note

Microsoft recommends using managed disks with Azure virtual machines (VMs) if possible. For more information about managed disks, see Azure Disk Storage overview for VMs.

Premium page blob storage accounts have the following scalability targets:

Total account capacity Total bandwidth for a locally redundant storage account
Disk capacity: 4 TB (individual disk)/ 35 TB (cumulative total of all disks)
Snapshot capacity: 10 TB
Up to 50 gigabits per second for inbound1 + outbound2

1 All data (requests) that are sent to a storage account

2 All data (responses) that are received from a storage account

A premium page blob account is be a general-purpose account configured for premium performance. General-purpose v2 storage accounts are recommended.

If you are using premium page blob storage accounts for unmanaged disks and your application exceeds the scalability targets of a single storage account, then Microsoft recommends migrating to managed disks. For more information about managed disks, see Azure Disk Storage overview for VMs.

If you cannot migrate to managed disks, then build your application to use multiple storage accounts and partition your data across those storage accounts. For example, if you want to attach 51-TB disks across multiple VMs, spread them across two storage accounts. 35 TB is the limit for a single premium storage account. Make sure that a single premium performance storage account never has more than 35 TB of provisioned disks.

See also