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

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


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

win-high-dpi

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/14a7eaba240000

📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/14a7eaba240000

Revert promises optimizations due to regressions in async hooks by mslekova@chromium.org
https://chromium.googlesource.com/v8/v8/+/91ddb65d3b34c07c5026727de84dc91b5e0a43cd

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions

Yeah this is expected, since we undid a couple of optimizations that also save memory. We'll get it back eventually.

Ups, we started working on this :-)

Automatic message: All alerts recovered.
Graphs: https://chromeperf.appspot.com/group_report?bug_id=847162

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/14b545b2640000

😿 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/14b545b2640000

Buildbucket says the build completed successfully, but Pinpoint can't find the isolate hash.