I believe that many people have asked this question and are depressed... Looking at the rise of dllhostmemory, we can see that the memory of aspnet_wp.exe%w3wp.exe is soaring...
From the Microsoft Product perspective, ASP/COM +/. NET may all have this problem. In the past, you needed adplus and other things and windbg to beat it. However, there will always be some so-called private symbols that make you unable to see the true colors of the mountains, not what you want to find mostProgramErrorCode.
Finally, we found two useful tools: debugdiag and CLR profiler. They are all Microsoft's things. Use them carefully, and they will never be used !!!
I have been working with Microsoft for four years and have done a lot of cases and learned a lot. Prepare for a closer look: how to optimize performance. If you have time, write it. If you don't have time, you can only talk about PPT.