When you want to profile an application using the Windows Performance Recorder, what options should you select? You will learn the recordings to select in the resource analysis section of the WPR UI menu and why you want to select those. You will also learn why you don't want to select every option there is.
- [Lecturer] Let's start the WPR UI by double clicking on the desktop shortcut we made earlier. Click yes on any prompts that come up. Let's now click on the drop down arrow where it says more options. This will display the performance recording profiles and performance scenario log settings. We want to make sure every check box is empty under First level triage, Resource Analysis, and Scenario Analysis. Now that we have set our options, let's click on the CPU usage box under Resource Analysis.
Next, let's make sure Performance scenario is set to General, Detail level is Verbose, and Logging mode is Memory. These are the settings that we'll use for the entire course. Even though there are many recording options, we only want to select CPU usage, since that is all we are interested in. The more options we select, the more overhead the Windows Performance Recording Tool itself will have. What this means is the more options we select, the more unreliable the CPU usage data becomes because the recording tool itself is consuming more of the CPU.
In order to be confident that the CPU data we see in the Windows Performance Analyzer is the closest to the house building usage, make sure you only have CPU usage checked. And that's it! That's the Windows Performance Record UI all set up and ready to record.
- Looking at single-threaded source code
- Collecting CPU data
- Call-stack walking
- Inspecting thread activity
- Transforming a single-threaded app into a multithreaded app