Azure-docs: Range configuration

[jackbond]

I realize this is preview, and it's definitely headed in the right direction, but please tell me this isn't how it's going to work post-preview...

"Containers can then scale instantly based on the workload needs within the 0.1*Tmax < T < Tmax range. "

As it stands, developers will still need to write cost saving logic to throttle databases all the way back down to 4000 RU/s (the min) during off peak hours. I have bulk insert operations, where 500,000RU will be awesome, but I'll have to write code to scale up, and then scale down. I realize you're going to lose some money on this, but please just give us a range selector, so we can set it to, 400RU <-> 500,000RU, and forget this .1Tmax nonsense.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: c5b2be67-25e0-a558-dae2-5fa149df2d96
• Version Independent ID: e95519f3-80f7-37bf-e3fc-9ebbf5081f17
• Content: Create Azure Cosmos containers and databases in autopilot mode.
• Content Source: articles/cosmos-db/provision-throughput-autopilot.md
• Service: cosmos-db
• GitHub Login: @kirillg
• Microsoft Alias: kirillg

[KalyanChanumolu-MSFT]

@jackbond Thank you for the detailed feedback.
When containers are configured in autopilot mode, they scale down to minimum throughput when not in use without additional work from the developer.

I believe you are requesting for a feature to configure the lower bound value to be .05 or 0.025 instead of 0.1*Tmax.

Tagging @markjbrown for info.

We actively listen to customer feedback and prioritize new features accordingly.

Please post this idea on UserVoice for other community members to vote and contribute as well.
You will also be notified when your feedback is triaged and implemented.

We will proceed to close this issue now.
If there are further questions regarding this matter, please comment and we will gladly continue the discussion.

[jackbond]

Actually, I don't want the lower bound to be a ratio at all. Ideally, we could set the lower bound to 100, and an upper bound to 500,000. I have lots of test databases that sit idle for weeks, perhaps even months. If the cloud is pay as you go (think functions), why isn't Cosmos? I understand paying some sort of minimum, but even the existing 400RU seems a bit pricey.

[AmitSuri]

The minimum bound should never be 400 or 2000 or X.
It should simply be 1 to Max. Why should anyone have to pay for something they are not using?

[markjbrown]

Agree on all points. Keep an eye on us towards Summer. Might have something in the works for you.

Thanks.