Azure environment respond very late for few seconds after deployment [Resolved]

Posted by Bhuvanesh6 under Azure on 10/17/2016 | Points: 10 | Views : 1624 | Status : [Member] | Replies : 1

Write New Post |

Search Forums | Answered

Resolved Posts |

Un Answered Posts |

Forums Home

When the MVC application is deployed to azure environment, there is slowness in page loading and also reponse time of web site get delayed for few seconds once the deployment is done.

Issue:
When the application is deployed in production environment, this slowness make the bad user experience.
Automation test scripts fails due to delay in reponse of site immediate after deployment

What we have tried:
Deployment is scheduled once in 30 days and also in mid night, however the user in other part of world face issues when deployment happens.

Can some one help me to resolve issue and there should not be any difference to user when deployment happens in producation.

Thanks in Advance.

Bhuvan

[Resolved]

Reply | Reply with Attachment

Alert Moderator

Responses

Posted by: Rajnilari2015 on: 10/18/2016 [Member] [Microsoft_MVP] [MVP] Platinum | Points: 50

0	Measures to minimize downtime and improve performance a) Enable "Always-On" for the Web App. By default, web apps are unloaded if they are idle for some period of time. This lets the system conserve resources. In Basic or Standard mode, you can enable Always On to keep the app loaded all the time. If your app runs continuous web jobs, you should enable Always On, or the web jobs may not run reliably. Read more at (https://azure.microsoft.com/en-us/documentation/articles/web-sites-configure/ ) b) Managed Pipeline Version Leave this set to Integrated (the default) unless you have a legacy app that requires an older version of IIS. c) Auto Swap If you enable Auto Swap for a deployment slot, App Service will automatically swap the web app into production when you push an update to that slot. Read more at ( https://azure.microsoft.com/en-us/documentation/articles/web-sites-staged-publishing/ ) 4) Make sure the Azure services are running close together. 5) Consider caching database content to a blob. 6) If the application is making DB calls, try to make as few round trips as possible by wrapping up the queries into a stored procedure. 7) Scale Up the web app in Azure Get more CPU, memory, disk space, and extra features like dedicated virtual machines (VMs), custom domains and certificates, staging slots, autoscaling, and more. Read more at (https://azure.microsoft.com/en-us/documentation/articles/web-sites-scale/ ) 8) Scale out the web app in Azure Increase the number of VM instances that run your app. Read more at ( https://azure.microsoft.com/en-us/documentation/articles/insights-how-to-scale/ ) 9) Use a profiler to figure out the problem. Read more at ( https://azure.microsoft.com/en-in/blog/remote-profiling-support-in-azure-app-service/ ) Equally you can have a look at ( https://blogs.msdn.microsoft.com/webdev/2014/07/29/profile-and-time-your-asp-net-mvc-app-all-the-way-to-azure/ ) for more information about performance improvement. Hope that will trigger you in the right direction. -- Thanks & Regards, RNA Team Bhuvanesh6, if this helps please login to Mark As Answer. \| Alert Moderator

Measures to minimize downtime and improve performance

a) Enable "Always-On" for the Web App.

By default, web apps are unloaded if they are idle for some period of time. This lets the system conserve resources. In Basic or Standard mode, you can enable Always On to keep the app loaded all the time. If your app runs continuous web jobs, you should enable Always On, or the web jobs may not run reliably.

Read more at (https://azure.microsoft.com/en-us/documentation/articles/web-sites-configure/ )

b) Managed Pipeline Version

Leave this set to Integrated (the default) unless you have a legacy app that requires an older version of IIS.

c) Auto Swap

If you enable Auto Swap for a deployment slot, App Service will automatically swap the web app into production when you push an update to that slot.

Read more at ( https://azure.microsoft.com/en-us/documentation/articles/web-sites-staged-publishing/ )

4) Make sure the Azure services are running close together.

5) Consider caching database content to a blob.

6) If the application is making DB calls, try to make as few round trips as possible by wrapping up the queries into a stored procedure.

7) Scale Up the web app in Azure

Get more CPU, memory, disk space, and extra features like dedicated virtual machines (VMs), custom domains and certificates, staging slots, autoscaling, and more.
Read more at (https://azure.microsoft.com/en-us/documentation/articles/web-sites-scale/ )

8) Scale out the web app in Azure

Increase the number of VM instances that run your app.

Read more at ( https://azure.microsoft.com/en-us/documentation/articles/insights-how-to-scale/ )

9) Use a profiler to figure out the problem. Read more at ( https://azure.microsoft.com/en-in/blog/remote-profiling-support-in-azure-app-service/ )

Equally you can have a look at ( https://blogs.msdn.microsoft.com/webdev/2014/07/29/profile-and-time-your-asp-net-mvc-app-all-the-way-to-azure/ ) for more information about performance improvement.

Hope that will trigger you in the right direction.

--
Thanks & Regards,
RNA Team

Bhuvanesh6, if this helps please login to Mark As Answer. | Alert Moderator

Latest Posts