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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgiqPxsgkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgyru0pgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgyqGGtwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgis-ZoQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgyqGGtwkM


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

chromium-rel-win7-dual

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

=== Auto-CCing suspected CL author ymalik@chromium.org ===

Hi ymalik@chromium.org, the bisect results pointed to your CL below as possibly
causing a regression. Please have a look at this info and see whether
your CL be related.


===== BISECT JOB RESULTS =====
Status: completed


===== SUSPECTED CL(s) =====
Subject : Implement the overflow-anchor CSS property as an opt-out for ScrollAnchoring
Author  : ymalik
Commit description:
  
This CL implements the opt-out described in the ScrollAnchoring explainer:
https://github.com/WICG/interventions/blob/master/scroll-anchoring/explainer.md

Intent to implement:
https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/TbuxbOtyZvk

BUG= 599180 

Review-Url: https://codereview.chromium.org/2145823002
Cr-Commit-Position: refs/heads/master@{#405368}
Commit  : 84452f6f0c65b006ca8646553147f3386e8b57ca
Date    : Thu Jul 14 00:42:55 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@405235  238.059  4.28922  27  good
chromium@405300  236.413  5.16056  62  good
chromium@405334  235.35   4.09055  62  good
chromium@405351  234.464  3.85192  62  good
chromium@405361  235.181  4.36857  62  good
chromium@405365  236.298  3.66847  62  good
chromium@405367  235.841  4.21279  41  good
chromium@405368  233.245  3.75266  62  bad    <--
chromium@405499  235.895  6.16024  27  bad
chromium@405762  234.677  4.6496   18  bad

Bisect job ran on: win_perf_bisect
Bug ID: 634983

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests speedometer
Test Metric: VanillaJS-TodoMVC/VanillaJS-TodoMVC
Relative Change: 1.78%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/win_perf_bisect/builds/6804
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9005148540891574864


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5906976211468288

| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Tests>AutoBisect.  Thank you!

This regression has been included in a stable release and that stable channel is now deprecated. I'm closing this so that we won't have unresponsive performance regressions in the future.