views:

45

answers:

3

The IIS http log tells me the time taken, so it's easy to identify long-running requests. But how can I identify the memory consumption of each request thread?

From within the process code I can easily get the size of the workingset for the entire process, but not of a request thread itself.

IIS 6 + Framework 3.5

Nick

+1  A: 

You could use a memory profiler such as the ANTS Memory Profiler from RedGate (14-free trial).

tvanfosson
A: 

I'm not sure that I'm reading you correctly but the threads are reused so there's no such thing as one thread per request. There's still hope, for instance you could set up a performance monitor log. Tess Ferrandez has quite a few articles on .NET memory debugging.

Or if you really want to dive in:

  1. adplus -hang -pn w3wp.exe -quiet
  2. Open the dump file in windbg
  3. !address -summary
Jonas Elfström
Thanks Jonas, your's is the only sensible response so far, others don't actually seem to understand the question. And even you weren't sure, so I'll rephrase it in a new question.
Nick
I must also try your diving suggestion, though I don't think it's going to provide me with what I'm seeking.
Nick