docs/profiling_content_shell_on_android.md - Issue 2545363002: Use HTTPS links for Google domains in docs

Side by Side Diff

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Side by Side Diff: docs/profiling_content_shell_on_android.md

Issue 2545363002: Use HTTPS links for Google domains in docs (Closed)

Patch Set: Modify two more files in subdirectories Created 4 years ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

View unified diff | Download patch

« no previous file with comments | « docs/piranha_plant.md ('k') | docs/retrieving_code_analysis_warnings.md » ('j') | no next file with comments »

OLD	NEW
1 # Profiling Content Shell on Android	1 # Profiling Content Shell on Android

2	2

3 Below are the instructions for setting up profiling for Content Shell on	3 Below are the instructions for setting up profiling for Content Shell on

4 Android. This will let you generate profiles for ContentShell. This will require	4 Android. This will let you generate profiles for ContentShell. This will require

5 linux, building an userdebug Android build, and wiping the device.	5 linux, building an userdebug Android build, and wiping the device.

6	6

7 [TOC]	7 [TOC]

8	8

9 ## Prepare your device.	9 ## Prepare your device.

10	10

(...skipping 76 matching lines...) Expand 10 before \| Expand all \| Expand 10 after Loading...
87 ## Run a Telemetry perf profiler	87 ## Run a Telemetry perf profiler

88	88

89 You can run any Telemetry benchmark with `--profiler=perf`, and it will:	89 You can run any Telemetry benchmark with `--profiler=perf`, and it will:

90	90

91 1. Download `perf` and `perfhost`	91 1. Download `perf` and `perfhost`

92 2. Install on your device	92 2. Install on your device

93 3. Run the test	93 3. Run the test

94 4. Setup symlinks to work with the `--symfs` parameter	94 4. Setup symlinks to work with the `--symfs` parameter

95	95

96 You can also run "manual" tests with Telemetry, more information here:	96 You can also run "manual" tests with Telemetry, more information here:

97 http://www.chromium.org/developers/telemetry/profiling#TOC-Manual-Profiling---An droid	97 https://www.chromium.org/developers/telemetry/profiling#TOC-Manual-Profiling---A ndroid

98	98

99 The following steps describe building `perf`, which is no longer necessary if	99 The following steps describe building `perf`, which is no longer necessary if

100 you use Telemetry.	100 you use Telemetry.

101	101

102 ## Use `adb_profile_chrome`	102 ## Use `adb_profile_chrome`

103	103

104 Even if you're not running a Telemetry test, you can use Catapult to	104 Even if you're not running a Telemetry test, you can use Catapult to

105 automatically push binaries and pull the profile data for you.	105 automatically push binaries and pull the profile data for you.

106	106

107 build/android/adb_profile_chrome --browser=content_shell --perf	107 build/android/adb_profile_chrome --browser=content_shell --perf

(...skipping 97 matching lines...) Expand 10 before \| Expand all \| Expand 10 after Loading...
205	205

206 ```	206 ```

207 adb pull /proc/kallsyms symbols/kallsyms	207 adb pull /proc/kallsyms symbols/kallsyms

208 ```	208 ```

209	209

210 1. Now add --kallsyms to your perfhost\_linux command:	210 1. Now add --kallsyms to your perfhost\_linux command:

211 ```	211 ```

212 ./perfhost_linux report -g -i perf.data --symfs symbols/ \	212 ./perfhost_linux report -g -i perf.data --symfs symbols/ \

213 --kallsyms=symbols/kallsyms	213 --kallsyms=symbols/kallsyms

214 ```	214 ```

OLD	NEW