Thursday, March 30, 2006
Quick things to check when you experience high memory levels in ASP.NET
When running your ASP.NET application if it stops responding at some point, there are few things you need to check. In the Task Manager, if you look at the ASP.NET Worker process (aspnet_wp.exe in IIS5.1 or w3wp in IIS 6.0) you will notice that the memory increases exponentially, if this is the case then check this article on MSDN.
I have listed below few settings required for optimum performance of your ASP.NET application.
Prior to deploying your application
o Set <compilation debug="false"...>
o Set <trace enabled="false" >
o Set <httpruntime executiontimeout="90"...>
Also check out the article Developing High-Performance ASP.NET Applications
I have listed below few settings required for optimum performance of your ASP.NET application.
Prior to deploying your application
o Set <compilation debug="false"...>
o Set <trace enabled="false" >
o Set <httpruntime executiontimeout="90"...>
Also check out the article Developing High-Performance ASP.NET Applications