Scalability and performance targets for the Azure Storage resource provider
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.
The service-level agreement (SLA) for Azure Storage accounts is available at SLA for Storage Accounts.
Scale targets for the resource provider
The following limits apply only when you perform management operations by using Azure Resource Manager with Azure Storage. The limits apply per region of the resource in the request.
| Resource | Limit |
|---|---|
| Storage account management operations (read) | 800 per 5 minutes |
| Storage account management operations (write) | 10 per second / 1200 per hour |
| Storage account management operations (list) | 100 per 5 minutes |