question

JasonLe-8865 avatar image
0 Votes"
JasonLe-8865 asked JasonLe-8865 commented

Does cosmos db auto increase throughput when throttle

The database was initially provisioned at 400k ru/s autoscale. I see provisioned throughput automatically increased from time to time. Right now, the data size has increased to 6.5TB, max throughput is now 3094k ru/s. It's much higher than minimum throughput requirement for storage. I do see light throttle occasionally. I wander if this is the reason database keep scaling out. Thanks

azure-cosmos-db
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

1 Answer

AnuragSharma-MSFT avatar image
0 Votes"
AnuragSharma-MSFT answered JasonLe-8865 commented

Hi @JasonLe-8865, welcome to Microsoft Q&A forum.

Yes Azure Cosmos DB automatically increases the throughput of database/container if storage size exceeds a limit. As per the article, "If the storage limit associated with the max throughput of the database or container is exceeded, Azure Cosmos DB will automatically increase the max throughput to the next highest RU/s that can support that level of storage.
For example, if you start with a max RU/s of 50,000 RU/s (scales between 5000 - 50,000 RU/s), you can store up to 500 GB of data. If you exceed 500 GB - e.g. storage is now 600 GB, the new maximum RU/s will be 60,000 RU/s (scales between 6000 - 60,000 RU/s)."

Please let me know if this information helps or else we can discuss further.


If answer helps, please mark it 'Accept Answer'




· 7
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

But the number does not add up. 6.5TB should require 650k RU/s. What I am seeing is 3094k RU/s. How do you explain that?

0 Votes 0 ·

Thanks for the reply. Could you please tell me how many containers do you have in the database? You can try based on below formula as well:

 MAX(4000, highest max RU/s ever provisioned / 10, current storage in GB * 100, 4000 + (MAX(Container count - 25, 0) * 1000)), rounded to nearest 1000 RU/s.

Limits for autoscale provisioned throughput

If this does not give the right calculation, we might need to raise a ticket with the support team. Please let me know.

0 Votes 0 ·

The database has 2 containers. It still won't add up.

0 Votes 0 ·
Show more comments