Sunday, November 25, 2018

Troubleshooting Azure for slow web app performance issues

Performance issues troubleshooting issues steps are like this:

This problem is often caused by application level issues, such as:
  • network requests taking a long time
  • application code or database queries being inefficient
  • application using high memory/CPU
  • application crashing due to an exception

Troubleshooting steps

A. Monitor your web app

This option enables you to find out if your application is having any issues. In your web app’s blade, click the Requests and errors tile. The Metric blade shows you all the metrics you can add.
Some of the metrics that you might want to monitor for your web app are
  • Average memory working set
  • Average response time
  • CPU time
  • Memory working set
  • Requests

B. Collect data

The Web Apps environment provides diagnostic functionality for logging information from both the web server and the web application. The information is separated into web server diagnostics and application diagnostics.

C. Mitigate the issue

Scale the web app

In Azure App Service, for increased performance and throughput, you can adjust the scale at which you are running your application. Scaling up a web app involves two related actions: changing your App Service plan to a higher pricing tier, and configuring certain settings after you have switched to the higher pricing tier.
For more information on scaling, see Scale a web app in Azure App Service.
Additionally, you can choose to run your application on more than one instance. Scaling out not only provides you with more processing capability, but also gives you some amount of fault tolerance. If the process goes down on one instance, the other instances continue to serve requests.
You can set the scaling to be Manual or Automatic.

Use AutoHeal

AutoHeal recycles the worker process for your app based on settings you choose (like configuration changes, requests, memory-based limits, or the time needed to execute a request). Most of the time, recycle the process is the fastest way to recover from a problem. Though you can always restart the web app from directly within the Azure portal, AutoHeal does it automatically for you. All you need to do is add some triggers in the root web.config for your web app. These settings would work in the same way even if your application is not a .Net app.
For more information, see Auto-Healing Azure Web Sites.

Restart the web app

Restarting is often the simplest way to recover from one-time issues. On the Azure portal, on your web app’s blade, you have the options to stop or restart your app.

You can feedback your opinion, whether its helpful or not

No comments:

Post a Comment