Open Bug 1772825 Opened 2 years ago Updated 5 months ago

[meta] Perf Sheriffing Improvements

Categories

(Testing :: Performance, task, P2)

Product:
Testing
Component:
Performance
Type:
task

Tracking

(Not tracked)

People

(Reporter: sparky, Unassigned)

References

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

Details

(Keywords: meta, Whiteboard: [fxp])

This bug is for making improvements to our perf-sheriffing workflow, and tooling. We need to do 3 major things here:

  1. Build up guidelines for handling alerts (including solution time frames, and severity guides for regressions).
  2. Improve response time for severe regressions.
  3. Improve comment 0 for developers. This includes adding more info about our tools, metrics, what the metrics means (and how they're obtained, etc.), how to debug the regression, what the extra options mean (e.g. cold, and warm), and a list of Do and don'ts (e.g. not using a VM to get representative numbers).

There is also the issue of how mitmproxy interfered with regressions but it's not exactly related to perf-sheriffing improvements.

Depends on: 1772827
Depends on: 1772828
Depends on: 1772829
Whiteboard: [fxp]
You need to log in before you can comment on or make changes to this bug.