Looking for strategies for using the CLR Profiler and ASP.NET

I have an Asp.Net application with some serious performance issues.

I thought I would try to identify problems by using the CLR Profiler, but I'm having some difficulty wading through all the data. The data includes all the underpinings of asp.net

Does anyone have a suggestion or three about how to trim the various graphs and trees down to "just my code" or to just one namespace?

1 Comment

Comments have been disabled for this content.