Imagine you are a developer and your boss comes to you complaining that your piece of code has been deemed to be taking up too much memory and causing problems for the application.  You take a look at your code and you see the following, assume that Read More......( read more )

I have talked about a bunch of commands used to troubleshoot a managed memory problem in the past and given some situations of using them like: High memory, CPU, or other performance problems with .NET High Memory continued - Datatables High Memory part Read More......( read more )

I wanted to get a feel for what tools people are using to test the performance of their website.  My questions are: Do you check page-load times?  Do you dig in to see which files are taking the time How do you track down a page that uses a Read More......( read more )

There are some times that you want to figure out what is taking up your memory.  There are a few ways that you can do this and some limitations put on this by .NET and ASP.NET. Memory in a dump file If you are looking at a dump file, the first thing Read More......( read more )

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......( read more )

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......( read more )

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......( read more )

So we already talked about what to gather when you are experiencing high memory .  But what if you are actually getting a System.OutOfMemoryException?  Here is how you capture a dump at the time you are running out of memory. The following steps Read More......( read more )

Identifying a Memory leak A Memory Leak in an IIS process (INETINFO.EXE, DLLHOST.EXE, W3WP.EXE) occurs when Memory Usage in Task Manager continues to consume more than 50% of the physical RAM until running out of system memory or until the process stops Read More......( read more )

A common problem we see when moving to .NET all revolves around the finalizer.  There are a few reasons that this happens: Developers move from C/C++ to C# and are used to created classes with a constructor and destructor. Developers don’t understand Read More......( read more )