For autoscale, we now provide recommendations through Azure Adviser that analyze the workload and suggest autoscale only if it would be cost beneficial.
In general, if utilization of the max RU/s across all hours in a month is averages to 66% or less you will save with autoscale. In addition, when using multi-region write setting with autoscale, the rate per 100 RU/s is the same for manual and autoscale.
An error occurred while saving the commentavi commented
reposting my comment from https://feedback.azure.com/forums/263030-azure-cosmos-db/suggestions/16598674-autoscale-throughput-ru-s:
As others have pointed out, it doesn't make sense to charge for the max RU/s per hour if said usage was used over a few seconds. It's obvious that this is to maximize returns from the autoscaling service, which I and others are very thankful for. Ideally the charge would be per second but it's understandable if it had to be max per minute or even max per 5-10 minutes for the overhead on your end but max per hour is ridiculous and conspicuous bad faith. Please address this, thanks.avi supported this idea ·
This is currently under review.avi shared this idea ·
Quick update. This was deferred for a while during 2021 but is back on plan. Will update as this work progresses.