Question：
Hello,
while investigating some memory issues on my new server (win2003 SP2), i stumbled upon very demotivating results which i have a hard time believing. This is what i did:
1) i created a new website and an application pool to go with it. The default config was left and i'm using ASP.NET 2.0
2) i created an ASP.NET page with the following code:
<%@ Page Language="C#" EnableSessionState="false" %>
<% Response.Write("this is a test."); %>
Next i opened up my task manager, found the right w3wp.exe process and checked the VM SIZE column. Here are the results:
1) First hit: memory goes to 28MB
2) Second hit: it increases by some 20KB
3) I launched a stress tool (10 users for half a minute) and the memory increases by 10MB.
So now the memory was up at about 40MB and it remained there.
Is this normal behaviour? For such a simple page, it seems unbelievable to see such a high memory usage, especially the increase with each request.
Is this really the best result i could expect from IIS 6.0 running ASP.NET 2.0 ?
Greg
Answer：
That's normal behavior. ASP.NET is pretty heavyweight because the .NET Run-time and the build system will be loaded into memory. When you start a stress-testing certain caches and data structures get created. Sooner or later the memory consumption might go down a little, e.g. if the Garbage Collector kicks in.
Hope this helps.
http://forums.iis.net/t/1154064.aspx