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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICglcvEqQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg1b7pqAoM


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

win-zenbook

Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8998424990437590304

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64_zen_perf_bisect/builds/556
Failure reason: the build has failed due to infrastructure failure.

Sorry, but I don't think we have the time to investigate this old report. There's a more serious performance regression on macOS which we are investigating in  Issue 657540 .