CosmosDB单个分区的吞吐量限制? [英] CosmosDB throughput limit of single partition?

查看:69
本文介绍了CosmosDB单个分区的吞吐量限制?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

在CosmosDB文档中,Microsoft提示单个分区的吞吐量限制,但未指定限制.我们是极限吗?这是相关的文档: https://docs.microsoft. com/en-us/azure/cosmos-db/partition-data

In the CosmosDB documentation, Microsoft hints at a throughput limit on a single partition, but does not specify the limit. We is the limit?. Here is the relevant documentation: https://docs.microsoft.com/en-us/azure/cosmos-db/partition-data

以及相关的引文:

在幕后,Azure Cosmos DB设置了为处理T个请求所需的分区.如果T高于每个分区的最大吞吐量 t,则Azure Cosmos DB设置N = T/t分区.

Behind the scenes, Azure Cosmos DB provisions partitions needed to serve T requests/s. If T is higher than the maximum throughput per partition t, then Azure Cosmos DB provisions N = T/t partitions.

推荐答案

没有明确回答您的问题,但是未明确提及此值的原因是因为随着Azure Cosmos DB团队的更改,它将被更改(增加)硬件,或推出硬件升级.目的是表明每个分区(机器)始终有一个限制,并且分区键将分布在这些分区之间.

Doesn't explicitly answer your question, but the reason this value is not explicitly mentioned is because it will be changed (increased) as the Azure Cosmos DB team changes hardware, or rolls out hardware upgrades. The intent is to show that there is always a limit per partition (machine), and that partition keys will be distributed across these partitions.

您可以通过以最大吞吐量饱和单个分区键的写入来发现当前值.

You can discover the current value by saturating the writes for a single partition key at maximum throughput.

这篇关于CosmosDB单个分区的吞吐量限制?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆