Make actions listed in perf regressions easy to follow, in developer-friendly language and clear |
|||
Issue descriptionFrom PM: """ sullivan: There is a really cool mock in that doc, but it's under the unprioritized long-term ideas. There are some simpler and more specific ideas, like having the bisect state the units of regressions. Can you be more specific on what addressing this action item would look like? sullivan: Overall the perf sheriffing action items in the postmortem are pretty vague, so it's hard to say if/when they are addressed. Would be great to clarify the most specific changes to be made. primiano: +sullivan@google.com happy to extract a subset of things from that PRD doc* that IMHO could have helped here. TL;DR I think that moving to a bug template that just says "Follow this regression on chromeperf.appspot.com/...?bug= 1234 " and that has all the summary of metrics affected and bisect results could have made easier for both sheriffs and author to understand the lab impact. * go/memory-speed-ops-prd """
,
Jul 24 2017
,
Jul 25 2017
I think, in the very near term, the alert should be at least changed to say something clearer than "⇗1.86 (59.44 +/- 17.51) MB". I have no idea what that means. Is it 1.86 MB or 59.44 +/- 17.51 MB?
,
Jul 25 2017
|
|||
►
Sign in to add a comment |
|||
Comment 1 by benhenry@chromium.org
, Jul 24 2017