Closed Bug 1379188 Opened 2 years ago Closed 11 months ago

Take a profile during talos tests and save the JSON to make regression analysis easier

Categories

(Testing :: Talos, defect)

Version 3
defect
Not set

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: bgrins, Unassigned)

References

Details

One thing that can make it difficult to track down regressions in talos tests is figuring out what specifically caused it to run slower. If we took profiles during test runs we could link to them from the treeherder alerts page and use perf-html.io to compare a regressed profile with a base profile.

I'm unsure of the performance overhead it would add, but if it's stable there would likely be a one time across the board regression without affecting alerts going forward.

This can be done with Services.profiler.StartProfiler / Services.profiler.StopProfiler / Services.profiler.dumpProfileToFileAsync. Alternatively in Bug 1250290, there's discussion of adding a MOZ_PROFILER_SHUTDOWN environment variable that would save the profile automatically.
Depends on: 1374333
we currently generate profiles for talos regressions- it is easy to do from treeherder now; we also collect daily profiles for all talos tests so we can reference profiles over time.
Status: NEW → RESOLVED
Closed: 11 months ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.