You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: support/azure/app-service/web-apps-performance-faqs.md
+28-12Lines changed: 28 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: Get answers to frequently asked questions about availability, perfo
4
4
author: genlin
5
5
ms.author: genli
6
6
ms.service: azure-app-service
7
-
ms.date: 03/05/2024
7
+
ms.date: 04/10/2025
8
8
ms.reviewer: toan, shrahman
9
9
---
10
10
# Application performance FAQs for Web Apps in Azure
@@ -28,6 +28,14 @@ The platform processes will consume a minimum amount of resources (such as CPU,
28
28
29
29
Multiple factors might contribute to slow app performance. For detailed troubleshooting steps, see [Troubleshoot slow web app performance](/azure/app-service/troubleshoot-performance-degradation).
30
30
31
+
> [!TIP]
32
+
> Enable the **Always On** setting under *Configuration > General settings* to keep your app warm and prevent cold starts. This helps reduce delay after idle time, especially in Basic and higher plans.
33
+
34
+
> [!TIP]
35
+
> Configure a **Health Check** path to monitor app health and automatically replace unresponsive instances. This helps maintain availability and performance.
## How do I troubleshoot a high CPU-consumption scenario?
32
40
33
41
In some high CPU-consumption scenarios, your app might truly require more computing resources. In that case, consider scaling to a higher service tier so the application gets all the resources it needs. Other times, high CPU consumption might be caused by a bad loop or by a coding practice. Getting insight into what's triggering increased CPU consumption is a two-part process. First, create a process dump, and then analyze the process dump. For more information, see [Capture and analyze a dump file for high CPU consumption for Web Apps](/archive/blogs/asiatech/how-to-capture-dump-when-intermittent-high-cpu-happens-on-azure-web-app).
@@ -38,8 +46,11 @@ In some high memory-consumption scenarios, your app might truly require more com
38
46
39
47
## How do I automate App Service web apps by using PowerShell?
40
48
41
-
You can use PowerShell cmdlets to manage and maintain App Service web apps. In our blog post [Automate web apps hosted in Azure App Service by using PowerShell](/archive/blogs/puneetgupta/automating-webapps-hosted-in-azure-app-service-through-powershell-arm-way), we describe how to use Azure Resource Manager-based PowerShell cmdlets to automate common tasks. The blog post also has sample code for various web apps management tasks.
42
-
For descriptions and syntax for all App Service web apps cmdlets, see [Az.Websites](/powershell/module/az.websites).
49
+
You can use PowerShell cmdlets to manage and maintain App Service web apps. In our blog post [Automate web apps hosted in Azure App Service by using PowerShell](/archive/blogs/puneetgupta/automating-webapps-hosted-in-azure-app-service-through-powershell-arm-way), we describe how to use Azure Resource Manager-based PowerShell cmdlets to automate common tasks.
50
+
51
+
> [!NOTE]
52
+
> For current automation scripts, use the latest **Az.Websites** module. The older `AzureRM` module is deprecated.
@@ -86,15 +97,6 @@ To see what is causing the error and to resolve the issue, follow the steps in [
86
97
87
98
For information about quotas and limits, see [App Service limits](/azure/azure-resource-manager/management/azure-subscription-service-limits#app-service-limits).
88
99
89
-
## How do I decrease the response time for the first request after idle time?
90
-
91
-
By default, web apps are unloaded if they're idle for a set period of time. This way, the system can conserve resources. The downside is that the response to the first request after the web app is unloaded is longer, to allow the web app to load and start serving responses. In Basic and Standard service plans, you can turn on the **Always On** setting to keep the app always loaded. This eliminates longer load times after the app is idle. To change the **Always On** setting:
92
-
93
-
1. In the Azure portal, go to your web app.
94
-
2. Select **Configuration**
95
-
3. Select **General settings**.
96
-
4. For **Always On**, select **On**.
97
-
98
100
## How do I turn on failed request tracing?
99
101
100
102
To turn on failed request tracing, follow these steps:
@@ -191,4 +193,18 @@ For more information about outbound connections in your web app, see the blog po
191
193
192
194
For a detailed walkthrough that shows you how to debug your web app by using Visual Studio, see [Remote debug your App Service web app](/archive/blogs/benjaminperkins/remote-debug-your-azure-app-service-web-app).
193
195
196
+
## Additional recommendations for performance and resiliency
197
+
198
+
> [!TIP]
199
+
> Use **Application Insights** and **Azure Monitor** for full-stack observability of your App Service app, including telemetry, dependency tracing, and live metrics.
200
+
201
+
> [!TIP]
202
+
> If you are deploying in regions that support **Availability Zones**, consider enabling zone redundancy for added resiliency during regional outages.
> App Service undergoes **routine maintenance** for platform reliability. For more control over update behavior, especially in App Service Environment v3, configure **Upgrade Preference** settings.
0 commit comments