I've been to talks like this one before, so not everything was new (in fact, very little was to me...which is probably a good thing, I guess). So, not as much struck me as interesting...but this is a (very) brief run down of some main points to take away...

1. Critical Problems are always...
1. IntraProcess: resources within the process like memory and CPU, or
2. InterProcess: contentions for resources outside (files, network, etc.)
2. Important CPU Counters to monitor for CPU utilization
1. % Processor Time: Useful in multi-CPU environments
2. % User Time: Determines how much work user-mode code in your app (therefore, typically YOUR APP) is taking,
3. % Priv. Time: Determines how much time the kernel is spent working on particular tasks given to it by your app.
3. Good CPU performance tools:
1. Visual Studio Performance Profiler (available in Team edition),
2. Kernrate viewer (available on MSDN),
3. Intel's performance profiler (forgot the name...oops)
4. Visual Studio Performance Profiler has the capability to profile in,
1. Sampling Mode: where it samples every N CPU cycles; this method is typically less intrusive, but given that it's time-based can miss things.
2. Instrumentation: performance code and bit are inserted into the runtime code, which takes up more time for it and gives it a larger working size, but is sometimes the only option for certain scenarios (like testing for Priv. Time slices).
5. Memory Problems:
1. Check for immense paging,
2. Tools:
1. Perf Counters, TaskManager, SysInternals' ProcessExplorer
2. CLRProfiler V 2.0
3. VADump (very cool app)
1. take note of the OtherData vs. Heap values in this as this determines what is native/managed resource leaks (usually) respectively.
4. Also Check out User Mode Dump Heap (never heard of this tool, personally), sometimes called "UMDH".
6. Key blogs:
1. http://blogs.msdn.com/ricom/.
2. http://blogs.msdn.com/maoni/.