CODEWITHSUNDEEP
azureazure-web-app-serviceazure-app-service-plansazure-app-service-envrmnt
Domenic
Domenic

Reputation: 738

Scaled out Azure App Service too slow

When I try to scale out my Azure Web App I experience very slow response times for requests on the second or third instance of the app. This seems to happen because the other instances were in cold mode and had to switch into hot mode once the load balancer redirected the request to them.

The problem is that in my scenario most of the time there isn't going on much on the system so probably only one instance will be used via the load balancer but approx four times a day there is a peak and I need more than one instance. But if these instances are in cold mode and had to wake up first it actually makes things worse.

The question is what to do?

I've already set the app to "always on" and ARR Affinity to "off".

In the past I've already experienced problems with my app going into some sort of sleep mode even though the app was set to "always on". I solved this by setting up a scheduler task that called the app every hour. But I don't think this would work with multiple instances anymore because the task would only call one instance and the other instances would still stay in sleep mode.

Any suggestions?

Upvotes: 6

Views: 1759

Answers (2)

ZERARI Mehdi
ZERARI Mehdi

Reputation: 11

increase your app service plan(S3) and try it again. I had similar problem and this solved it.

Alternatively, you can reconfigure your scaling rules.

Upvotes: 1

Andy Shen
Andy Shen

Reputation: 992

Consider enabling logging to debug which instances are receiving the requests and why these requests are slow.

For the comment around four times a day, you need more than once instance -- consider setting up Autoscale with recurrence profile on your app service plan to automatically scale out. You can setup autoscale rule with different instance counts based on the time of day.

Upvotes: 0

Related Questions