How can we improve Azure Cosmos DB?

Autoscale Throughput (UR/s)

Depending on the average amount of incomming requests/ required RU's, (or other parameters,)
I would like to autoscale the througput(RU/s) of a collection.

1,501 votes
Vote
Sign in
(thinking…)
Sign in with: Microsoft
Signed in as (Sign out)
You have left! (?) (thinking…)
tjgalama shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

57 comments

Sign in
(thinking…)
Sign in with: Microsoft
Signed in as (Sign out)
Submitting...
An error occurred while saving the comment
  • Colin Webber commented  ·   ·  Flag as inappropriate

    Is there any update or ETA on this?
    It's been almost 2 years at this point. My team is implementing CosmosDB for SessionState and Distributed caching across numerous projects and this feature will be crucial for controlling costs while still responding to peaks in traffic throughout the day effectively.

  • Santosh commented  ·   ·  Flag as inappropriate

    Auto Scale RUs will be good feature.However Currently RUs are charged pe rhour rather than charging for the time for which RUs are upscaled.
    For instance, if you increase provisioned throughput at 9:30 AM from 400 RU/s to 1000 RU/s and then lower provisioned throughput at 10:45 AM back to 400 RU/s, you will be charged for two hours of 1000 RU/s.
    Can we change the pricing to the amount of time RUs being upscaled ,because it will surge the billing

  • Russ commented  ·   ·  Flag as inappropriate

    This really is mandatory as we are getting hit by peak loads that mean I have to have the RU's to match, a very expensive model.

  • Anonymous commented  ·   ·  Flag as inappropriate

    We are waiting for this to enable consumption based functions. It's no good having functions scale out under load and been throttled at the database.

    Is there any update around timeline on this?

  • Luke commented  ·   ·  Flag as inappropriate

    How in the world isn't this feature available and why is Microsoft Azure ignoring all of these comments?

  • [Deleted User] commented  ·   ·  Flag as inappropriate

    CosmosDB provides great functionalities especially with the new ********* model by now. We have quite unexpected load on production and if auto scaling of throughput mechanism is not provided by Microsoft, we will not consider to shift to CosmosDB.

  • Prasad commented  ·   ·  Flag as inappropriate

    Cloud is Pay as you Go but as Auto scaling feature is not provided it is really difficult to manage manually RUs for Cosmos. Auto scaling provision is must needed.

  • Brett Davis commented  ·   ·  Flag as inappropriate

    We're extremely interested in this feature as well - we have a lot of services with hard-to-estimate production loads beforehand and we end up finding out that we are getting throttled when we just happen to dig down through the metrics to the right collection after it's seen some traffic. We have tons of services with their own DBs and collections and trying to set up scaling monitors for each new service is an extremely impractical solution for us.

  • Morrolan commented  ·   ·  Flag as inappropriate

    Wow, this is still not a feature? This was one of the larger reasons I decided not to use cosmos. Such a pain to run jobs to up the RU's, and then put them down again, and handle when task fails you don't want the collections left set high. Pain to deal with this stuff, when it should be all taken care of in a managed service.

← Previous 1 3

Feedback and Knowledge Base