Short version (executive summary! ): What is the most appropriate method of measuring memory use within IIS 5.1... Long version: I'm hitting the 100Mb app pool limit, but can't easily test this out on my XP Pro dev machine as 5.1 doesn't support app pools. I've tried Scitechs memory profiler (realtime graph and AddRealTimeComment are quite cool), along with GC.GetTotalMem, and though it has pointed me in the direction of peak memory usage (Xmldocs are real hogs!), it doesn't go over the 100Mb. So given that I have recycled the app pool before I start and have no other apps running, there must be some overhead that I'm not factoring in. Any thoughts? Thanks to a previous post I'm also going to see whether the health monitoring will give me more info when the limit is exceeded, as my existing application_end code never gets executed in this instance (which appears to be a known shortcoming with unexpected shutdowns) And a quick pat-on-the-back for the support guys here at discountasp.net: both tickets I raised were answered promptly with exactly the information I needed, or more. For comparison, my experience with my previous company over at easycgi.com was to fob you off for a day or more, then pass you on to the technical experts for a, usually, totally irrelevant answer. Thank you!
Hi, Health monitoring will probably be the best way. I've asked Joe Stagner to create a Webcast for that for Shared Hosting and he told me it is in the works, will be available on the ASP.NET Learning section when complete. You can Search MSDN there are some resources for it there but rather scattered. ;-) Salute, Mark
