Tom Christian's Blog : Hang

Web Site Stops Responding for 15-25 seconds

ASP.NET Debugging : IIS — Tue, 28 Oct 2008 10:00:00 GMT

There are a number of reasons that a web site could have a delay (hang) that could cause problems. I am going to talk about a common one that we see which is the CRL. What we have seen in the past is the Crypto API’s are trying to update the Certificate...(read more)

ASP.NET and Performance

ASP.NET Debugging : IIS — Mon, 23 Jun 2008 18:29:34 GMT

I wanted to talk about monitoring performance in ASP.NET for a bit. I have already posted a few postings that talk around this issue, namely: ASP.NET Debugging - High Memory part 5 – Fragmentation ASP.NET Debugging - ASP.NET Tips- How to use DebugDiag...(read more)

ASP.NET Tips: What to gather to troubleshoot

ASP.NET Debugging : IIS — Wed, 21 May 2008 15:38:59 GMT

So now that I am done with all the individual posts, I thought I would wrap them all together. So here are all of the posts that I created on gathering information when you are having a problem. Please keep in mind that these are geared towards...(read more)

ASP.NET Tips: What to gather to troubleshoot - part 4 - Deadlocks

ASP.NET Debugging : IIS — Wed, 14 May 2008 15:35:09 GMT

There are two ways to gather data in a Deadlock situation. If you are using Windows 2003 or later (IIS 6.0 or later), then follow the steps in the KB 828222 If you are using an older version of IIS, then follow the steps below: Before the issue...(read more)

POP QUIZ: How to Troubleshoot a Hang

ASP.NET Debugging : IIS — Wed, 07 May 2008 13:31:14 GMT

For this quiz. Let’s say that you run a web server and your customers complain that the site is running slow. What do you do to troubleshoot it? As a follow-up, if you figure out that one page is the problem, what do you do to look into what...(read more)

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

ASP.NET Debugging : IIS — Fri, 25 Apr 2008 19:54:00 GMT

We recently had a case where the customer was having performance problems. They were seeing requests take a few minutes to return and didn’t know what was happening. So they took some dumps while the problem was happening. So we ran this dump through...(read more)