Azure Web Role “warm up” strategies [closed]
I found that making requests to our web role after periods on inactivity would result in a very slow request (up to 30 seconds). After that initial request, the role would perform as it should. After much Googling, I came across four different strategies (listed below): (a) Disabling IIS idle timeout in RoleEntryPoint.OnStart() public override bool OnStart() { using (var server = new ServerManager()) { server.ApplicationPoolDefaults.ProcessModel.IdleTimeout = TimeSpan.Zero; server.CommitChanges(); } return base.OnStart(); } This also requires that the role runs at an elevated level. (b)