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)