Slides from my ”Best Practices for managed code investigations’ talk


Today I gave a talk entitled ‘Best Practices for managed code investigations’, but what it really is a overview of the PerfView tool. 

I have posted the slides below.   Unfortunately, most of the talk was a demo which of course don’t show up on the slides, there is still some good material there.

The main theme of the talk however was to

  1. Simply get people to try the PerfView tool
  2. Indicate that the tool can handle a  broad variety of problems (Memory, CPU, blocked time, GC clitches, startup time ….)
  3. Thus it is worth investing in the tool (learning more about it)

Vance

 

BestPractices.pptx


Comments (2)

  1. Todd says:

    How can I use PerfView to look at performance of a web application, specifically IIS (w3wp) process with ASP.Net running? All I currently see is a command path that can be suppllied or the entire machine…

  2. vancem says:

    The Collect -> Collect memu entry turns on collection machine wide.   Thus you simply start perfview on the machine, run your scenario (if your server is under load, you just have to wait say 10 seconds), and then hit the 'stop' button.  

    PerfView has a special view that shows you bulk ASP.NET stats (like requests per second, mean and maximum responce time etc).   I often start there, since these are the statistics you probably care the most about.

    PerfView can drill into particular requests.  I will probably blog about that sometime soon (right now I am a bit swamped).