请求率过大，已将数据库预配置为15.000 RU [英] Request rate is too large, with a Database provisioned to 15.000 RU

问题描述

我有一些代码，我在20个并行任务中以每100个文档的批次插入20.000个文档，并且由于请求率太大"异常而受到限制.

我将Cosmos DB设置为在数据库级别支持15.000 RU.

现在，100个文档* 20 = 2000个文档称呼.每个文档看起来都是这样，并且都在1kb以下:

{

解决方案

安德斯，

几个问题:

在数据库级别将R/U设置设置为15k(15,000)的情况下，这些文档是否也以15k(15,000)写入集合?

客户端每秒将多少文档写入API?

我拿了您的示例文件，并将其用于Cosmos DB估计和大小计算器中，并且将R/U设置为15k(15,000或15.000)，每秒可以写入该接口的最大文档数刚好超过1000/秒:

估算请求单位和数据存储

但是随后有一个以5k(5,000或5.000)配置的集合:

因此，完全有可能以15,000的价格配置数据库，但集合设置为不相同?！

Hi,

I have some code, where I insert 20.000 Documents, in batches of 100 Documents in 20 parallel tasks, and I am being throttled with the Exception "Request rate is too large"

I provisioned my Cosmos DB to support 15.000 RU at Database level.

now, 100 Docs * 20 = 2000 Documents pr. call. Each Document looks like this, and is way under 1kb:

{

解决方案

Hi Anders,

A few questions:

In the case that the R/U setting is set to 15k (15,000) at the database level, is the collection these documents are being written to also at 15k (15,000)? 

How many documents per second are being written to the API by the client? 

I took your example file and used it in the Cosmos DB estimation and sizing calculator and with an R/U set to 15k (15,000 or 15.000), the max documents you can write to the interface is just slightly over 1000 per second:

Estimate Request Units and Data Storage

As an example, I have a Database that is provisioned at 10k (10,000 or 10.000):

But then have a Collection that is provisioned at 5k (5,000 or 5.000):

So, it is entirely possible that the Database was provisioned at 15,000 but the Collection was not set to the same?!

这篇关于请求率过大，已将数据库预配置为15.000 RU的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！