高级页 blob 存储帐户的可伸缩性和性能目标Scalability and performance targets for premium page blob 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.

高级页 blob 帐户的缩放目标Scale targets for premium page blob accounts

高级性能页 blob 存储帐户已针对读取/写入操作进行了优化。A premium-performance page blob storage account is optimized for read/write operations. 这种类型的存储帐户支持 Azure 虚拟机的非托管磁盘。This type of storage account backs an unmanaged disk for an Azure virtual machine.

Note

Microsoft 建议尽可能在 Azure 虚拟机 (VM) 中使用托管磁盘。Microsoft recommends using managed disks with Azure virtual machines (VMs) if possible. 有关托管磁盘的详细信息,请参阅用于 Windows VM 的 Azure 磁盘存储概述For more information about managed disks, see Azure Disk Storage overview for Windows VMs.

高级页 blob 存储帐户有以下可伸缩性目标:Premium page blob storage accounts have the following scalability targets:

总帐户容量Total account capacity 本地冗余存储帐户的总带宽Total bandwidth for a locally redundant storage account
磁盘容量:4 TB(单个磁盘)/35 TB(所有磁盘的累计总数)Disk capacity: 4 TB (individual disk)/ 35 TB (cumulative total of all disks)
快照容量:10 TBSnapshot capacity: 10 TB
为入站1 和出站2 流量提供最高 50 Gbps 的带宽Up to 50 gigabits per second for inbound1 + outbound2

1 发送到存储帐户的所有数据(请求)1 All data (requests) that are sent to a storage account

2 从存储帐户接收的所有数据(响应)2 All data (responses) that are received from a storage account

高级页 blob 帐户是针对高级性能配置的通用帐户。A premium page blob account is be a general-purpose account configured for premium performance. 建议使用常规用途 v2 存储帐户。General-purpose v2 storage accounts are recommended.

如果对非托管磁盘使用高级页 blob 存储帐户并且应用程序超过了单个存储帐户的可伸缩性目标,Azure 建议迁移到托管磁盘。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 Azure recommends migrating to managed disks. 有关托管磁盘的详细信息,请参阅用于 Windows VM 的 Azure 磁盘存储概述用于 Linux VM 的 Azure 磁盘存储概述For more information about managed disks, see Azure Disk Storage overview for Windows VMs or Azure Disk Storage overview for Linux 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. 例如,如果要将 51-TB 的磁盘附加到多个 VM,请将这些磁盘分散在两个存储帐户中。For example, if you want to attach 51-TB disks across multiple VMs, spread them across two storage accounts. 35 TB 是单个高级存储帐户的限制。35 TB is the limit for a single premium storage account. 请确保单个高级性能存储帐户永远不会超过 35 TB 的预配磁盘。Make sure that a single premium performance storage account never has more than 35 TB of provisioned disks.

另请参阅See also