Currently, I'm working on web app scaling out configuration.
My goal is to create additional instances as soon as the CPU increases to 40% or more. I've done some configuration and it works.
Here is my configuration.
But the problem is that it responds to the metrics not immediately. Usually, it takes a few minutes before scaling and this is something that is not acceptable in my case.
Is it possible to make the scaling process respond to metrics changes faster?
Hi, here is a best practices articles on this process: https://docs.microsoft.com/en-us/azure/azure-monitor/autoscale/autoscale-best-practices#choose-the-thresholds-carefully-for-all-metric-types
There is also a preview feature for predictive autoscaling for Virtual Machine Scale Sets (not App Service) which might be of interest as an alternative option for you: https://docs.microsoft.com/en-us/azure/azure-monitor/autoscale/autoscale-predictive
Thanks for the links.
Unfortunately, I haven't found an answer to my question - how to make the app service plan scale-out respond to CPU changes as soon as possible?
I don't think there is a way currently. The scale out operation does take some time to complete. If the issue is due to performance impact until the scale out operation completes then I think your best option for this service is to adjust your scaling logic to try and scale out a bit earlier in order to handle the increased load before there is a noticeable performance impact.
17 people are following this question.
