TestEngineering/Performance/Talos/Profiling: Difference between revisions

Jump to navigation Jump to search
no edit summary
(Restoring this page and making the Buildbot page redirect here.)
No edit summary
Line 3: Line 3:
When profiling is enabled, we use the [https://developer.mozilla.org/en-US/docs/Mozilla/Performance/Profiling_with_the_Built-in_Profiler Gecko Profiler] to capture profiles during each Talos run that can then be displayed by [https://perf-html.io perf.html]. The captured profiles are grouped into zip files, one per Talos test, which are placed into the upload directory.
When profiling is enabled, we use the [https://developer.mozilla.org/en-US/docs/Mozilla/Performance/Profiling_with_the_Built-in_Profiler Gecko Profiler] to capture profiles during each Talos run that can then be displayed by [https://perf-html.io perf.html]. The captured profiles are grouped into zip files, one per Talos test, which are placed into the upload directory.


== On [https://wiki.mozilla.org/Build:TryServer TryServer] ==
== 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:
Confirmed users
2,177

edits

Navigation menu