CODEWITHSUNDEEP
asp.net-mvcasp.net-mvc-4azureazure-web-app-service
SamJolly
SamJolly

Reputation: 6477

Struggling with the issue of "Cold" code in Standard Azure Websites

I am using MVC3, ASP.NET4.5, EF5, SQL Azure.

I currently use external auto ping services (pingdom and uptime robot) pinging specific urls, not all, to try to keep the site warm. I have noticed that certain parts, perhaps which have not be used since a refresh, particularly to do with DB updates, run slowly to start with.

I understand "Always On" could be a big help, but I am unsure whether it is better than external auto ping services like pingdom? Is it more pervasive within the application?

Many thanks.

Upvotes: 2

Views: 103

Answers (2)

Zain Rizvi
Zain Rizvi

Reputation: 24656

Yes, "Always On" does exactly what the name sounds like. It keeps the site constantly warm and running, which is exactly what you're trying to do with an external auto ping service. Note that this only is available for Basic and Standard sites.

More details on "Always On" here: https://stackoverflow.com/a/21841469/21539

Upvotes: 3

Amit Apple
Amit Apple

Reputation: 9192

In addition to Zain's answer, one more thing "Always On" does is that it keeps all of your instances (VMs) for the website alive and this is something an external pinger will not do as it will ping and get only one of the instances of your website each time.

Upvotes: 4

Related Questions