Skip to content

Commit 4c17d2c

Browse files
committed
Add profiling docs hint for output file
1 parent 162b946 commit 4c17d2c

File tree

1 file changed

+2
-3
lines changed

1 file changed

+2
-3
lines changed

docs/Profiling.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -68,8 +68,7 @@ int Application::run() {
6868

6969
## Show results
7070

71-
The resulting JSON file uses
72-
the [Trace Event Format](https://docs.google.com/document/d/1CvAClvFfyA5R-PhYUmn5OOQtYMH4h6I0nSsKchNAySU/preview). Any
71+
The resulting JSON file (`profile.json`) uses the [Trace Event Format](https://docs.google.com/document/d/1CvAClvFfyA5R-PhYUmn5OOQtYMH4h6I0nSsKchNAySU/preview). Any
7372
tool that can read this format can visualize the profiler data. For example the web
7473
tool [Perfetto](https://ui.perfetto.dev/) or Chromes built in [chrome://tracing](chrome://tracing). Just drag&drop the
7574
generated profiler JSON file onto the tool to load it.
@@ -78,6 +77,6 @@ This is roughly how this looks like on Chrome.
7877

7978
![chrome-trace.png](assets/chrome-trace.png)
8079

81-
***
80+
---
8281

8382
Next up: [Logging](Logging.md)

0 commit comments

Comments
 (0)