Closed Bug 1668055 Opened 4 years ago Closed 3 years ago

Run profiler in marker only mode on high priority performance tests

Categories

(Testing :: Performance, enhancement, P3)

Product:
Testing
Component:
Performance
Type:
enhancement

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 1635522

People

(Reporter: kimberlythegeek, Unassigned)

References

(Depends on 1 open bug, Blocks 1 open bug)

Details

It has been suggested that running the profiler on all performance tests would be beneficial in analyzing performance regressions, but the high overhead of the profiler would have a significant performance impact, and consume a lot of resources.

However, the profiler can be run in marker-only mode, save both time and resources. This will build on the work to add profile markers to the performance tests.

  1. Determine what tests are both high priority and would benefit from profiles
  2. Decide how frequently the tests should run: every run? every X runs?
  3. Configure specified tests to run at that frequency
Severity: -- → S3
Priority: -- → P3

This would be quite nice, especially after getting consistent markers across the test suites. Here is an additional UI ideas that might help visualize these markers:

https://github.com/firefox-devtools/profiler/issues/2803

Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.