Confirmed users
821
edits
TestEngineering/Performance/Talos/Profiling: Difference between revisions
TestEngineering/Performance/Talos/Profiling (view source)
Revision as of 07:22, 2 July 2020
, 2 July 2020Replaced occurrences of perf-html.io to profiler.firefox.com
(Restoring this page and making the Buildbot page redirect here.) |
m (Replaced occurrences of perf-html.io to profiler.firefox.com) |
||
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
= How to Run Talos in Profiling Mode = | = How to Run Talos in Profiling Mode = | ||
When profiling is enabled, we use the [https:// | When profiling is enabled, we use the [https://profiler.firefox.com Firefox Profiler] to capture profiles during each Talos run that can then be displayed by [https://profiler.firefox.com profiler.firefox.com]. The captured profiles are grouped into zip files, one per Talos test, which are placed into the upload directory. | ||
== On [ | == On [[ReleaseEngineering/TryServer|TryServer]] == | ||
1. When you push to try, add "mozharness: --gecko-profile" after "try: ..." to your commit message. Example: | 1. When you push to try, add "mozharness: --gecko-profile" after "try: ..." to your commit message. Example: | ||
| Line 13: | Line 13: | ||
./mach try fuzzy --gecko-profile | ./mach try fuzzy --gecko-profile | ||
2. When the test(s) finishes, select the job on treeherder, and click on the 'Job Details' tab. You will see the resulting talos 'profile_*' artifacts listed, with a link beside each one, to open it in [https:// | 2. When the test(s) finishes, select the job on treeherder, and click on the 'Job Details' tab. You will see the resulting talos 'profile_*' artifacts listed, with a link beside each one, to open it in [https://profiler.firefox.com profiler.firefox.com].] | ||
[[File:Talos profiling artifacts screenshot.png|800x461px]] | [[File:Talos profiling artifacts screenshot.png|800x461px]] | ||
| Line 23: | Line 23: | ||
After the Talos run is done, you will have a zip file with multiple profiles in your Talos "upload dir", which is, by default, at <code>testing/mozharness/build/blobber_upload_dir</code>. | After the Talos run is done, you will have a zip file with multiple profiles in your Talos "upload dir", which is, by default, at <code>testing/mozharness/build/blobber_upload_dir</code>. | ||
Talos will automatically launch Firefox and load the latest talos gecko profile in [https:// | Talos will automatically launch Firefox and load the latest talos gecko profile in [https://profiler.firefox.com profiler.firefox.com]. To turn this feature off, just set the DISABLE_PROFILE_LAUNCH=1 env var. | ||
If auto-launch doesn't work for some reason, just start Firefox manually and browse to [https:// | If auto-launch doesn't work for some reason, just start Firefox manually and browse to [https://profiler.firefox.com profiler.firefox.com], click on "Browse" and select the talos profile zip file noted above. | ||
If you're on Windows and want to profile a Firefox build that you compiled yourself, make sure it contains profiling information and you have a symbols zip for it, by following the [https://developer.mozilla.org/en-US/docs/Mozilla/Performance/Profiling_with_the_Built-in_Profiler_and_Local_Symbols_on_Windows#Profiling_local_talos_runs directions on MDN]. | If you're on Windows and want to profile a Firefox build that you compiled yourself, make sure it contains profiling information and you have a symbols zip for it, by following the [https://developer.mozilla.org/en-US/docs/Mozilla/Performance/Profiling_with_the_Built-in_Profiler_and_Local_Symbols_on_Windows#Profiling_local_talos_runs directions on MDN]. | ||