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

Tuesday, March 21, 2006


Some more random AJAX thoughts

Speaking of Atlas/AJAX. Do you think it is really useful -- or otherwise -- here is a post on Rick Strahl's blog I recently came across.

I am back, so is Atlas

I couldn't blog for a while due to my commitment to the new job, yes I switched my job. The new place is better and allows me to work in my full capacity, we are heading towards working with ASP.NET 2.0 soon -- that will be a alot more exciting though.

Atlas in the news again, with its March CTP out a while ago, to go behind-the-scenes and see what's new -- check out Nikhil's post.

This page is powered by Blogger. Isn't yours?