Changes

Jump to: navigation, search

TestEngineering/Performance/Raptor

54 bytes added, 07:17, 2 July 2020
m
Replaced occurrences of perf-html.io to profiler.firefox.com
=== Profiling Raptor Jobs ===
Raptor tests are able to create Gecko profiles which can be viewed in [https://perf-htmlprofiler.iofirefox.com/ perf-htmlprofiler.firefox.iocom.] This is currently only supported when running Raptor on Firefox desktop.
==== Nightly Profiling Jobs in Production ====
Note: While profiling is turned on, Raptor will automatically reduce the number of pagecycles to 3. If you wish to override this, add the --page-cycles argument to the raptor command line.
Raptor will automatically launch Firefox and load the latest Gecko profile in [https://perf-htmlprofiler.io perfhtmlfirefox.iocom 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://perf-htmlprofiler.io perfhtmlfirefox.iocom profiler.firefox.com], click on "Browse" and select the Raptor 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].
# Click on the 'Job Details' tab below
# The Raptor profile ZIP files will be listed as job artifacts;
# Select a Raptor profile ZIP artifact, and click the 'view in perf-html.ioFirefox Profiler' link to the right
=== Recording Pages for Raptor Pageload Tests ===
Confirm
820
edits

Navigation menu