ASP.NET Tips: How to use DebugDiag to track down where a performance problem is coming from

ASP.NET Tips: How to use DebugDiag to track down where a performance p

DotNetKicks.com — Fri, 25 Apr 2008 22:54:51 GMT

You've been kicked (a good thing) - Trackback from DotNetKicks.com

ASP.NET Tips: How to use DebugDiag to track down where a performance problem is coming from

Useful IIS/ASP.NET Information provided by Microsoft Support Teams — Fri, 25 Apr 2008 23:01:32 GMT

Narrowing down a problem is sometimes the hardest part of troubleshooting.  Learn how DebugDiag

ANSWER: POP QUIZ: Troubleshoot a Hang

ASP.NET Debugging — Thu, 08 May 2008 20:26:44 GMT

We got some really good answers to this quiz.  I am going to give my answer but it isn’t the only

re: ASP.NET Tips: How to use DebugDiag to track down where a performance problem is coming from

Joshi — Thu, 08 May 2008 22:00:42 GMT

Hey Tom, I wanted to know what is the impact on the server when we capture dumps using Debugdiag, Especially when we enable leak track

re: ASP.NET Tips: How to use DebugDiag to track down where a performance problem is coming from

Tom — Thu, 08 May 2008 23:10:45 GMT

Debugdiag doesn't have much impact other then the CPU and hard drive space needed to create the dump. Enabling Leak Track is a bit more. As it will track any allocations that happen, but it will only be in that process. The impact on the server should be minimal.

re: ASP.NET Tips: How to use DebugDiag to track down where a performance problem is coming from

Roberto Santoro — Thu, 16 Jul 2009 11:36:43 GMT

Hey Tom,

I'm sorry but I don't understand how do you find out which is the thread which is executing the long running request (basically how do you go from step 2 to step 3.

Thanks,

Roberto.

re: ASP.NET Tips: How to use DebugDiag to track down where a performance problem is coming from

Tom — Tue, 21 Jul 2009 05:59:30 GMT

Roberto,

You get the client connections list in the debug diag report and you just look for one that has been running for a long time. Like that request had been running for 2 minutes and 46 seconds.