12
edits
Buildbot/Talos/Profiling: Difference between revisions
Jump to navigation
Jump to search
no edit summary
(Created page with "= How to Run Talos in Profiling Mode = When profiling is enabled, we use the [https://developer.mozilla.org/en-US/docs/Mozilla/Performance/Profiling_with_the_Built-in_Profile...") |
No edit summary |
||
| Line 28: | Line 28: | ||
3. Download the zip file from this URL, extract it and see [https://developer.mozilla.org/en-US/docs/Mozilla/Performance/Profiling_with_the_Built-in_Profiler#Upload_and_Share_the_Profile_to_Cleopatra this] page for info about how to open profiles in cleopatra. | 3. Download the zip file from this URL, extract it and see [https://developer.mozilla.org/en-US/docs/Mozilla/Performance/Profiling_with_the_Built-in_Profiler#Upload_and_Share_the_Profile_to_Cleopatra this] page for info about how to open profiles in cleopatra. | ||
= FAQ = | |||
== The Talos results with profiling are always higher == | |||
Yes, profiling usually has non-trivial overhead. This is why you might want to try one of these two approaches: | |||
* Do a Talos run with profiling on before and after your change and compare those numbers. | |||
* Do a Talos run with profiling off to check if the issue still exists and at the same time do a run with profiling on to get the data from it. | |||