Lets talk about a scenario here and take a look at manual way to find what we need with windbg + sos.We will then see how we can automate this using Debug Analyzer.NET Analysis. For learning pleasure and reuse, attached code snippet can be saved in snippets folder and used with Instant Analyzer feature too.

ScenarioAn intranet ASP.NET application becomes very slow during off-peak hours. Since it's during off peak hours we can guess that it might not be due to heavy load.There are several different tools and ways to troubleshoot this issue using profiling tools etc... But since running profiler etc might not be a great idea on production servers, we will use memory dumps to get the users who are using the application and then check what they are doing during that specific time of the issue.(Maybe running a slow moving, large report?)

Related posts

Welcome to Debug Analyzer.NET !Having a job where you need to deal with memory dumps for customer issues, it’s always good to...Architecture & DesignFrom my experience as a developer I have seen a lot of great applications from architectur...AboutHi my name is Sukesh, I'm sure you must've figured that out by now. I'm a technology geek and my cor...