On a production environment, how can one discover which Asp.Net http
requests, whether aspx or asmx or custom, are causing the most memory
pressure within a w3wp.exe process? I don't mean memory leaks here. It's a
good healthy application that disposes all it's objects nicely. Microsoft's
generational GC does it's work fine. Some requests however, cause the w3wp
process to grow its memory footprint considerably, but only for the duration
of the request.

It is simply a question of the cost-efficiency and scalability of a
production environment for a SAAS app, in order to regularly report back to
the development department on their most memory hogging "pages", and to
return that (memory) pressure where it belongs, so to speak.

There doesn't seem to be anything like:
HttpContext.Request.PeakPrivateBytes or .CurrentPrivateBytes
or
Session.PeakPrivateBytes

No one?

"Nick" wrote: