All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=828351

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=294a7bca096b881015530afae8b45df011b9c47eac1d18e250ca9db4d3330dc0


Bot(s) for this bug's original alert(s):

webrtc-mac-large-tests

Not sure what others do, but when sheriffing I try to link alerts on perf-related reverts to the same bug as the original problem (i.e., triage button and "existing bug").

Do you see any useful action on this issue, besides closing?

FYI, I just relanded the change, hopefully with the perf problem fixed.

Ok, the interface warns you that the alerts aren't overlapping when you do that so I thought it was discouraged. Will to that the next time.

No, just closing as wontfix is usually what people do.

Expected change from revert.