Confirmed users
372
edits
Buildbot/Talos/Profiling: Difference between revisions
Jump to navigation
Jump to search
m
→Updated when running Talos locally
| Line 21: | Line 21: | ||
If you're running Talos using <code>mach talos-test</code>, you only need to append <code>--geckoProfile</code> to the command and the rest should happen automatically. | If you're running Talos using <code>mach talos-test</code>, you only need to append <code>--geckoProfile</code> to the command and the rest should happen automatically. | ||
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://perf-html.io perfhtml.io]. To turn this feature off, just set the TALOS_DISABLE_PROFILE_LAUNCH=1 env var. | |||
If auto-launch doesn't work for some reason, just start Firefox manually and browse to [https://perf-html.io perfhtml.io], 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]. | ||