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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgor3u9AgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgoq_rvwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgosX-oAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg4vCLpAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgws_Z4AgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgopHLtwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgopH6qgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgouupuwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgoqL-pgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgwoWYoQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgwr-0rwkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgwrvyrQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgwr-0rwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgoqufvQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgoqH_sQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgovmVpQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgop2FswoM


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

chromium-rel-mac-retina
chromium-rel-mac10
chromium-rel-mac11
chromium-rel-win7-dual
chromium-rel-win7-gpu-ati
chromium-rel-win7-gpu-intel
chromium-rel-win7-single
chromium-rel-win7-x64-dual
chromium-rel-win8-dual
win-zenbook

Moving this nonessential bug to the next milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Lan, can you follow up on this?

From the instructions (https://chromium.googlesource.com/chromium/src/+/master/tools/perf/docs/perf_regression_sheriffing.md):
"After your shift, please try to follow up on the bugs you filed weekly. Kick off new bisects if the previous ones failed, and if the bisect picks a likely culprit follow up to ensure the CL author addresses the problem. If you are certain that a specific CL caused a performance regression, and the author does not have an immediate plan to address the problem, please revert the CL."

The regression is recovered, and mark it as wontfix.