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

表存储的可伸缩性和性能目标Scalability and performance targets for Table 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.

表存储的缩放目标Scale targets for Table storage

下表描述了表存储的容量、可伸缩性和性能目标。The following table describes capacity, scalability, and performance targets for Table storage.

资源Resource 目标Target
Azure 存储帐户中表的个数Number of tables in an Azure storage account 仅受存储帐户的容量限制Limited only by the capacity of the storage account
表中的分区个数Number of partitions in a table 仅受存储帐户的容量限制Limited only by the capacity of the storage account
分区中实体的个数Number of entities in a partition 仅受存储帐户的容量限制Limited only by the capacity of the storage account
单个表的最大大小Maximum size of a single table 500 TiB500 TiB
单个实体的最大大小,包括所有属性值Maximum size of a single entity, including all property values 1 MiB1 MiB
表实体中属性的最大数目Maximum number of properties in a table entity 255(包括 3 个系统属性:PartitionKeyRowKeyTimestamp255 (including the three system properties, PartitionKey, RowKey, and Timestamp)
实体中单个属性的最大总大小Maximum total size of an individual property in an entity 因属性类型而异。Varies by property type. 有关详细信息,请参阅了解表服务数据模型中的属性类型For more information, see Property Types in Understanding the Table Service Data Model.
PartitionKey 的大小Size of the PartitionKey 大小最大为 1 KiB 的字符串A string up to 1 KiB in size
RowKey 的大小Size of the RowKey 大小最大为 1 KiB 的字符串A string up to 1 KiB in size
实体组事务的大小Size of an entity group transaction 一个事务最多可包含 100 个实体,并且有效负载大小必须小于 4 MiB。A transaction can include at most 100 entities and the payload must be less than 4 MiB in size. 实体组事务只能包含对实体的更新一次。An entity group transaction can include an update to an entity only once.
每个表存储的访问策略的最大数目Maximum number of stored access policies per table 55
每个存储帐户的最大请求速率Maximum request rate per storage account 20,000 事务/秒,假定实体大小为 1-KiB20,000 transactions per second, which assumes a 1-KiB entity size
单个表分区的目标吞吐量(1 KiB 实体)Target throughput for a single table partition (1 KiB-entities) 每秒最多 2,000 个实体Up to 2,000 entities per second

另请参阅See also