My understanding with scaling is that it is a simple sum total of how long it would take to provision all the resources that come under the service plan. You said, you have 8 app services and 2 function apps. Try to think back to how long it took to provision them. If each app took about a minute, then, it would be roughly 10 minutes. for example, if your app has a cosmos db, that along would take anywhere from 3 to 10 minutes. i am speaking based on my own experience.
So, now, to your questions.
- What reasons are effecting to the scale time? (number of resources, apps?)
Yes individual apps and the resources they depend on are a huge factor in deciding the scale time.
- What can I do to reduce the manual scale time? ( I mean the best practice of configuration)
not much. this is one of those that is outside your control.
However, if I were you, I would consider moving some of the apps and functions out of this service plan, and may be manage them individually?
Let's say I have a web app with a database service. I find out that the server is able to handle the load just fine, but it is the database that needs a bigger plan. Then, instead of keeping them on the same plan, i would move the database to a separate plan, only focus the scaling efforts on the database and leave the web app service alone.
- If we apply auto-scale to this ASP, will it scale faster?
No.