Performance tracing with HoloLens is a powerful way to find and resolve computational or hardware bottlenecks. When traces are analyzed with the Windows Performance Analyzer, you’re able to visualize and explore hardware or software bottlenecks. Examples of this might be something that’s causing a HoloLens to overheat or CPU processes that are especially taxing on the system.
Performance Trace Analysis in WPA
To get a detailed understanding of system and application behavior and resource usage for HoloLens, you can use the performance tracing feature. This feature captures Windows Performance Recorder traces in the form of an event trace log (ETL) file for use in the Windows Performance Analyzer (WPA).
To analyze a trace file, download WPA from the Microsoft Store.
For more general purpose debugging tools, you can also use the Windows Performance Toolkit. To get this toolkit, download the Windows Assessment and Deployment Kit.
When searching for information about performance traces, you’ll inevitably come across a range of terms. The most important ones are:
Term | Definition |
---|---|
ETW | Event Tracing for Windows: The overarching name for kernel-level tracing facility that’s built into Windows. |
ETL | Event Trace Log: The file extension for files that store the tracing data. Thus, when you do a trace, you typically will have an *.etl file afterwards. |
WPR | Windows Performance Recorder: The application that starts and stops the recording of event traces. WPR takes a profile file (*.wprp) that configures which exact events to log. Below, you’ll learn how to do a trace for HoloLens through the Windows Device Portal. |
WPA | Windows Performance Analyzer: A GUI application that’s used to open *.etl files and sift through data to identify performance issues. WPA allows you to sort data by various criteria, display the data in several ways, dig down into details, and correlate information. |
Generate an ETL file using the Device Portal in your HoloLens.
Performance tracing page in Device Portal for HoloLens 2
You now have an ETL file that you can either open directly in WPA or send to someone else.
Windows Performance Analyzer is the standard tool to visualize traces as graphs and tables to allow you to analyze system and application performance. WPA is a powerful, multifaceted tool, so we won’t explain it in detail here. For more detail, use the Step-by-step guide to use Windows Performance Analyzer.
To learn more about WPA, have a look at these resources:
Files you need for WPA trace analysis
There are several files you’ll need to analyze your trace file in WPA. We’ve included an example WPA profile to help you get started.
(*.etl)
(*.pdb)
. Make sure it’s extracted (not zipped).(*.wpaProfile)
. Use this example WPA Profile for CPU analysis.Set up your files in a folder for WPA to access them.
Example
Folder_for_WPA_files
├─ HoloLens_trace_file.elt - # HoloLens trace file (*.etl)
├─ CPU_analysis.wpaProfile - # WPA Profile (*.wpaProfile)
└─ Symbols - # Make sure it's extracted (not zipped).
├─ *.pdb
├─ *.pdb
└─ ...
.etl
in your file browser.
:::image type=”content” source=”images/WPA-open-trace-ETL-file-red-highlight.png” alt-text=”Image of WPA with File menu expanded and Open action selected.”:::[!TIP] Configure extra symbol paths by selecting Trace > Configure Symbol Paths. :::image type=”content” source=”images/configure-symbols-extra-symbols.jpg” alt-text=”Configure symbols for WPA analysis.”:::
*.wpaProfile
file > Apply.Dive Deeper
To learn more about WPA, see the WPA documentation.
Dive deeper into WPA or learn more about performance tracing.