您现在访问的是微软AZURE全球版技术文档网站,若需要访问由世纪互联运营的MICROSOFT AZURE中国区技术文档网站,请访问 https://docs.azure.cn.

Blob 存储的可伸缩性和性能目标Scalability and performance targets for Blob storage

此参考详细说明了 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.

Blob 存储的缩放目标Scale targets for Blob storage

资源Resource 确定目标Target
单个 blob 容器的最大大小Maximum size of single blob container 与最大存储帐户容量相同Same as maximum storage account capacity
块 blob 或附加 blob 中块的最大数目Maximum number of blocks in a block blob or append blob 50,000 块50,000 blocks
块 blob 中块的最大大小Maximum size of a block in a block blob 100 MiB100 MiB
块 blob 的最大大小Maximum size of a block blob 50000 X 100 MiB (约 4.75 TiB)50,000 X 100 MiB (approximately 4.75 TiB)
追加 blob 中块的最大大小Maximum size of a block in an append blob 4 MiB4 MiB
追加 blob 的最大大小Maximum size of an append blob 50000 x 4 MiB (约 195 GiB)50,000 x 4 MiB (approximately 195 GiB)
页 blob 的最大大小Maximum size of a page blob 8 TiB8 TiB
每个 blob 容器的最大存储访问策略数Maximum number of stored access policies per blob container 55
单个 blob 的目标请求速率Target request rate for a single blob 每秒最多500个请求Up to 500 requests per second
单页 blob 的目标吞吐量Target throughput for a single page blob 最高每秒 60 MiBUp to 60 MiB per second
单个块 blob 的目标吞吐量Target throughput for a single block blob 最多存储帐户入口/出口限制1Up to storage account ingress/egress limits1

1单个 blob 的吞吐量取决于多个因素,包括但不限于:并发、请求大小、性能层、上传源的速度,以及下载的目标。1 Throughput for a single blob depends on several factors, including, but not limited to: concurrency, request size, performance tier, speed of source for uploads, and destination for downloads. 若要利用高吞吐量块 blob的性能增强功能,请上传更大的 blob 或块。To take advantage of the performance enhancements of high-throughput block blobs, upload larger blobs or blocks. 具体而言,为标准存储帐户使用大于 4 MiB 的 blob 或块大小调用Put blobput 块操作。Specifically, call the Put Blob or Put Block operation with a blob or block size that is greater than 4 MiB for standard storage accounts. 对于高级块 blob 或 Data Lake Storage Gen2 存储帐户,请使用大于 256 KiB 的块或 blob 大小。For premium block blob or for Data Lake Storage Gen2 storage accounts, use a block or blob size that is greater than 256 KiB.

另请参阅See also