Skip to content

Commit df48ad7

Browse files
author
Michael Zappe
committed
Dots in alt text and correct section link
1 parent 953d8d5 commit df48ad7

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

articles/remote-rendering/how-tos/performance-tracing.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,7 @@ While ETL traces can be created on any Windows device (local PC, HoloLens, cloud
4444

4545
## Recording a trace on a local PC
4646

47-
Use traces on PC to either get familiar with the tools or if you have an issue where the hardware restrictions of the HoloLens aren't relevant. Otherwise you can skip to the [Recording a trace on a HoloLens](#Recording-a-trace-on-a-HoloLens) section. Especially ARR performance issues should only be traced directly on a HoloLens.
47+
Use traces on PC to either get familiar with the tools or if you have an issue where the hardware restrictions of the HoloLens aren't relevant. Otherwise you can skip to the [Recording a trace on a HoloLens](#recording-a-trace-on-a-hololens) section. Especially ARR performance issues should only be traced directly on a HoloLens.
4848

4949
### WPR configuration
5050

@@ -60,7 +60,7 @@ Use traces on PC to either get familiar with the tools or if you have an issue w
6060

6161
Afterwards your WPR configuration should look like this:
6262

63-
![WPR configuration](./media/wpr.png)
63+
![WPR configuration.](./media/wpr.png)
6464

6565
### Recording
6666

@@ -74,7 +74,7 @@ You now have an ETL file that you can open in WPA.
7474

7575
To record a trace on a HoloLens, boot up your device and enter its IP address into a browser to open up the *Device Portal*.
7676

77-
![Device Portal](./media/wpr-hololens.png)
77+
![Device Portal.](./media/wpr-hololens.png)
7878

7979
1. On the left, navigate to *Performance > Performance Tracing*.
8080
1. Select **Custom profiles**.
@@ -122,7 +122,7 @@ Windows Performance Analyzer is the standard tool to open ETL files and inspect
122122

123123
To get started with ARR tracing, the following pieces are good to know.
124124

125-
![Performance graph](./media/wpa-graph.png)
125+
![Performance graph.](./media/wpa-graph.png)
126126

127127
The image shows a table of tracing data and a graph representation of the same data.
128128

@@ -134,15 +134,15 @@ All **columns to the left of the yellow bar** are interpreted as **keys**. Keys
134134

135135
The columns in the middle have no special meaning.
136136

137-
![Events view](./media/wpa-event-view.png)
137+
![Events view.](./media/wpa-event-view.png)
138138

139139
In the *Generic Events View Editor* you can configure all the columns to display, the aggregation mode, sorting and which columns are used as keys or for graphing. In the example image, **Field 2** is enabled and Field 3 - 6 are disabled. Field 2 is typically the first *custom data* field of an ETW event and thus for ARR "FrameStatistics" events, which represent some network latency value. Enable other "Field" columns to see further values of this event.
140140

141141
### Presets
142142

143143
To properly analyze a trace, you need to figure out your own workflow, and preferred data display. However, to be able to get a quick overview over the ARR-specific events, we include Windows Software Protection Platform profile and presets files in the folder *Tools/ETLProfiles*. To load a full profile, select *Profiles > Apply...* from the WPA menu bar, or open the *My Presets* panel (*Window > My Presets*) and select *Import*. The former sets up a complete WPA configuration as in the image below this paragraph. The latter only makes presets for the various view configurations available and allow you to quickly open a view to look at a specific piece of ARR event data.
144144

145-
![Presets](./media/wpa-arr-trace.png)
145+
![Presets.](./media/wpa-arr-trace.png)
146146

147147
The image shows views of various ARR-specific events plus a view of the overall CPU utilization.
148148

0 commit comments

Comments
 (0)