Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We are running a number of ASP.NET applications on W2K3 Server and IIS 6.0, and are looking for a way to be able to monitor ASP.NET session state variables (InProc) that are stored in memory. We are thinking there may be some memory optimization opportunities with some of these session state variables potentially consuming large amounts of RAM.

Is there a way to accomplish this through IIS or Windows rather than instrumenting all of the individual Web apps with code to monitor the session state variables?

share|improve this question
up vote 2 down vote accepted

If you can reproduce your sessions that you think use too much memory in a dev environment, then the .Net CLR Profiler and its development web server are a good way to go about this. Here is a blog post that outlines the process of setting up the profiler and and pull InProc session data from it.

If you can only pull the data from production, things get harder, but not impossible. See chapter 2 of the .Net Framework Production Debugging guide - it tells you how to pull memory data from running IIS processes that you should be able to analyze.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.