chromium/src
0
Fork 0
Code Activity

Update profiling.md with link to internal tools

Browse Source 
I thought about linking to a shared doc that said these same things,
but this documentation seems to have everything I would want to say.

Change-Id: I027ac5e9f6e5a6925306e405ae36e0c1f6fcf938
Reviewed-on: https://chromium-review.googlesource.com/c/1407948
Reviewed-by: Stefan Zager <szager@chromium.org>
Commit-Queue: enne <enne@chromium.org>
Cr-Commit-Position: refs/heads/master@{#622258}
This commit is contained in:
Adrienne Walker
2019-01-12 01:51:41 +00:00
committed by Commit Bot
parent b7c0c06fb6
commit e24f71a487
1 changed files with 7 additions and 0 deletions

7
docs/profiling.md

@ -192,3 +192,10 @@ The perf benchmark runner can generate a CPU profile over the course of running
$ src/tools/perf/run_benchmark run <benchmark name> --interval-profiling-target=renderer:main --interval-profiling-period=interactions --interval-profiling-frequency=2000
The profiling data will be written into the `artifacts/` sub-directory of your perf benchmark output directory (default is `src/tools/perf`), to files with the naming pattern `*.profile.pb`. You can use `pprof` to view the results, as described above.
## Googlers Only
If you use `pprof -proto chrome-profile-renderer-12345` to turn your perf data
into a proto file, you can then use that resulting file with internal tools.
See [http://go/cprof/user#fs-profiles](http://go/cprof/user#fs-profiles])
for instructions on how to go about this.