Browse by Tags

• .NET
• ASP.NET
• Debugging
• Hang
• High CPU
• High Memory
• IIS
• Microsoft

ASP.NET and Performance

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...

Posted 23 June 08 02:29 by Tom | 2 Comments   
Filed under ASP.NET, Debugging, IIS, Crash, .NET, High Memory, Microsoft, ASP.NET Tip, Hang, High CPU

ASP.NET Tips: What to gather to troubleshoot

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...

Posted 21 May 08 11:38 by Tom | 3 Comments   
Filed under ASP.NET, Debugging, IIS, Crash, .NET, High Memory, ASP.NET Tip, Hang, High CPU

ASP.NET Tips: What to gather to troubleshoot - part 6 - Recycle due to memoryLimit

Here is another situation that you may come across and what to do in order to gather information about it. The following steps will configure DebugDiag to automatically capture a memory dump of the ASPNET_WP.exe process recycling when it exceeds the memoryLimit.  Read More...

Posted 20 May 08 12:03 by Tom | 4 Comments   
Filed under ASP.NET, Debugging, IIS, Crash, .NET, High Memory, ASP.NET Tip

ASP.NET Tips: What to gather to troubleshoot - part 3a - Crash revisited

In the previous post around capturing a dump for a crash, we were talking about using DebugDiag .  But what if we can't use this tool.  There are various reasons for this, maybe we don't want to have it installed on the server, or maybe we are Read More...

Posted 15 May 08 11:11 by Tom | 4 Comments   
Filed under ASP.NET, Debugging, Crash, .NET, ASP.NET Tip

ASP.NET Tips: What to gather to troubleshoot – part 3 – Crash

Defining an IIS Crash A Crash in IIS occurs when an IIS process (INETINFO.EXE, DLLHOST.EXE, W3WP.EXE) terminates unexpectedly. A Crash typically happens when there is an Unhandled Exception caused by an Access Violation, Stack Overflow, etc. In these Read More...

Posted 06 May 08 11:39 by Tom | 5 Comments   
Filed under ASP.NET, Debugging, IIS, Crash, ASP.NET Tip

Search

This Blog

• Home
• Email