In this post, we enhance the simple custom profile for WPR by adding the system tracing session. Because kernel events provide critical information about processes, threads, modules, and more, collecting the system events greatly extends your ability to analyze traces and diagnose issues.
This is the first post in a multi-part series about authoring custom profiles for Windows Performance Recorder (WPR.) In a previous post, we have looked at how to start a trace with built-in profiles. The built-in profiles offer wide variety of preset profiles that we can use for different scenarios. There are built-in profiles for CPU usage, Ne...
In this post, we show how to start and stop the trace using WPR. The first step is doing 'wpr -help start'. The command parameters seems to be cryptic. We explain those parameters in detail with examples.
If you do a search online for WPA, you might find information for protecting your Wi-Fi, but that is a different type of WPA. In the performance & diagnostics space WPA stands for Windows Performance Analyzer, a friendly but intricate UI that allows for developers and analyst to deep dive into performance traces captured on Windows (and beyo...
This is the first blog post about WPR. WPR is an acronym for Windows Performance Recorder. This post introduces list of acronyms that are used commonly performance tools, installation steps, the difference between WPR and WPRUI, and finally about the instance name and the error.
