Earlier this week, Teemu Keiski asked me if I knew of a way to check the memory consumption of AppDomains in a process. You may ask why there was multiple AppDomains in a process -- because the server that he was running the ASP.NET applications was Windows 2000. There has been quite a bit of guess work from my end of what could be going wrong and why?
Eventually, I came to conclude that it was an application that was always "washing" in and out a huge collection from the database. There were several constraints on what he could do: it was a live server so he could not profile any application as such. The one thing that really frustrated both of us is that the misbahving application could be pinpointed. Or can it?
I just ran over this article from www.TheServerSide.com. And it is awesome! Wish I knew of this method earlier.