I have a single web role containing a couple of web sites and some web services (all very lightly used). For many months, these have been .NET 4.0 and running with no issues at all. One of the web sites makes a call to one of the web services and, previously,
has always received an instant response from the service. It was also the case that once one of the web sites had been accessed, the initial access to any of the others was instant. I have now migrated to .NET 4.5 and the corresponding newer Azure version.
Now, when the web site calls the web service, I am seeing a delay around 30 seconds. Also, the initial access to any of the web sites is taking a similar amount of time. It's as if something is working differently either in .NET 4.5 or Azure - perhaps separate
app pools for each site, where they were all combined before? That's a pure guess. I'd welcome some wisdom on what is happening here, and the best way to combat it. Thanks, Nick
I've now found some time to have a closer look at this. It's definitely a delay in the initial startup of each web site/service. Reading other threads on here confirms that each site/service will run in its own application pool. Is that a change in .NET
4.5 and/or Azure 2012, or has it always been like that?
The startup delay is definitely a new phenomenon since the move to .NET 4.5 and Azure 2012 - there were no application changes made at the same time.
I still need some help to understand what is happening here and, more importantly, how to stop it.
NickLocke
Member
92 Points
147 Posts
.NET 4.5 and "2012" behaving differently?
Dec 22, 2012 08:43 PM|LINK
HostingASPNe...
All-Star
15882 Points
2977 Posts
Re: .NET 4.5 and "2012" behaving differently?
Dec 23, 2012 07:30 AM|LINK
Hello,
If the delay is in the initial loading you could try to increase the applicaition pool timeout value.
Regards
Free ASP.NET Examples and source code.
NickLocke
Member
92 Points
147 Posts
Re: .NET 4.5 and "2012" behaving differently?
Jan 05, 2013 09:19 PM|LINK
I've now found some time to have a closer look at this. It's definitely a delay in the initial startup of each web site/service. Reading other threads on here confirms that each site/service will run in its own application pool. Is that a change in .NET 4.5 and/or Azure 2012, or has it always been like that?
The startup delay is definitely a new phenomenon since the move to .NET 4.5 and Azure 2012 - there were no application changes made at the same time.
I still need some help to understand what is happening here and, more importantly, how to stop it.
Cheers,
Nick