标准存储帐户的可伸缩性和性能目标Scalability and performance targets for standard storage accounts

本参考详细介绍了 Azure 存储的可伸缩性和性能目标。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.

当应用程序达到分区能够处理的工作负荷极限时,Azure 存储将开始返回错误代码 503(服务器忙)或错误代码 500(操作超时)响应。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. 如果发生 503 错误,请考虑修改应用程序以使用指数退避策略进行重试。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 standard storage accounts

下表介绍 Azure 常规用途 v1、v2 和 Blob 存储帐户的默认限制。The following table describes default limits for Azure general-purpose v1, v2, and Blob storage accounts. “传入” 限制是指请求中发送到存储帐户的所有数据。The ingress limit refers to all data from requests that are sent to a storage account. “传出” 限制是指响应中从存储帐户接收的所有数据。The egress limit refers to all data from responses that are received from a storage account.

资源Resource 默认限制Default limit
每个订阅每个区域的存储帐户数,包括标准帐户和高级帐户Number of storage accounts per region per subscription, including both standard and premium accounts 250250
最大存储帐户容量Maximum storage account capacity 5 PiB 15 PiB 1
每个存储帐户的 Blob 容器、Blob、文件共享、表、队列、实体或消息数目上限Maximum number of blob containers, blobs, file shares, tables, queues, entities, or messages per storage account 无限制No limit
每个存储帐户的最大请求速率1Maximum request rate1 per storage account 每秒 20,000 个请求20,000 requests per second
每个存储帐户的最大入口1Maximum ingress1 per storage account 如果已启用 RA-GRS/GRS,则为 5 Gbps;对于 LRS,为 10 Gbps25 Gbps if RA-GRS/GRS is enabled, 10 Gbps for LRS2
常规用途 v2 存储帐户和 Blob 存储帐户的最大流出量(所有区域)Maximum egress for general-purpose v2 and Blob storage accounts (all regions) 50 Gbps50 Gbps
常规用途 v1 存储帐户的最大出口Maximum egress for general-purpose v1 storage accounts 如果已启用 RA-GRS/GRS,则为 10 Gbps;对于 LRS,为 15 Gbps210 Gbps if RA-GRS/GRS is enabled, 15 Gbps for LRS2
每个存储帐户的虚拟网络规则数目上限Maximum number of virtual network rules per storage account 200200
每个存储帐户的 IP 地址规则数目上限Maximum number of IP address rules per storage account 200200

1Azure 存储标准帐户根据请求支持更高的容量上限和更高的流入量上限。1Azure Storage standard accounts support higher capacity limits and higher limits for ingress by request. 若要请求提高帐户入口上限,请与 Azure 支持联系。To request an increase in account limits for ingress, contact Azure Support.

2 如果存储帐户启用了异地冗余存储 (RA-GRS) 的读取访问权限,则辅助位置的出口目标与主位置的出口目标相同。2 If your storage account has read-access enabled with geo-redundant storage (RA-GRS), then the egress targets for the secondary location are identical to those of the primary location. Azure 存储复制选项包括:Azure Storage replication options include:

Note

大多数情况下,Azure 建议使用常规用途 v2 存储帐户。Azure recommends that you use a general-purpose v2 storage account for most scenarios. 可以轻松将常规用途 v1 或 Azure Blob 存储帐户升级到常规用途 v2 帐户,无需停机且无需复制数据。You can easily upgrade a general-purpose v1 or an Azure Blob storage account to a general-purpose v2 account with no downtime and without the need to copy data. 有关详细信息,请参阅升级到常规用途 v2 存储帐户For more information, see Upgrade to a general-purpose v2 storage account.

如果应用程序的需求超过单个存储帐户的伸缩性目标,则可以构建使用多个存储帐户的应用程序。If the needs of your application exceed the scalability targets of a single storage account, you can build your application to use multiple storage accounts. 然后,可以将数据对象分布到这些存储帐户中。You can then partition your data objects across those storage accounts. 有关批量定价的信息,请参阅 Azure 存储定价For information on volume pricing, see Azure Storage pricing.

所有存储帐户都在扁平网络拓扑上运行,无论它们创建于何时,都支持本文所述的可伸缩性和性能目标。All storage accounts run on a flat network topology and support the scalability and performance targets outlined in this article, regardless of when they were created. 有关 Azure 存储的扁平网络体系结构和可伸缩性的详细信息,请参阅 Azure Storage: A Highly Available Cloud Storage Service with Strong Consistency(Azure 存储:具有高度一致性的高可用云存储服务)。For more information on the Azure Storage flat network architecture and on scalability, see Azure Storage: A Highly Available Cloud Storage Service with Strong Consistency.

另请参阅See also