If you are using InProc session state, all your session data is stored in w3wp's memory, and may be the cause of it growing.
pgb
2009-10-22 23:45:45
A:
Indeed that is the case, and that is another thing I want to measure: the memory footprint of each session.So what I would like are things like...HttpContext.Request.PeakPrivateBytesSession.PeakPrivateBytes
Nick
2009-10-23 00:02:11
A:
I wouldn't worry about it. It could be that the GC is happening during the request, and the CLR is allocating memory to move things around. Or it could be some other periodic servicing thing that comes along with ASPNET.
Unless you are prepared to go spelunking with perf counter analysis of generation 0,1,2 GC events , and etc, then I wouldn't worry about solving this "problem".
And it doesn't sound like it's a problem anyway - just a curiosity thing.
Cheeso
2009-10-22 23:46:00
Sorry no kudo's here. You're certainly quick on the trigger, but obviously haven't understood the nature of the question.
Nick
2009-10-22 23:53:39
A:
Hi Nick,
You might want to use a tool like Performance Monitor to monitor the "Process\Working Set" for the W3WP.exe process and record it to a database. You then could could correlate it to the HTTP logs for the IIS Server.
It helps to have both the Perfmon data and HTTP logs both writing to an SQL database. Then you can use T-SQL to bring up requested pages by Date/Time around the time of the observed memory pressure. Use the DatePart function to build a Date/Time rounded to the desired accuracy of Second or Minute as needed.
Hope this helps.
Thanks, -Glenn
Glenn
2009-11-13 14:14:26
Thanks Glenn,Your suggestion is the only serious response I've had so far, having posted this same question in several MSDN forums and also over at ServerFault.com.Regarding you suggestion, that certainly would be feasible, but would also entail alot of work. One problem I can already see in correlating the data is that IIS HTTP logs the end time of a request and not the start time. Tho IIS 7 offers Advanced Logging.It does surprise me that in this world of SAAS and Web 2.0 (or are we at 3.0 now?) nobody else seems to be this interested in the memory behaviour of their web applications.
Nick
2009-11-17 10:03:28