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

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


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

chromium-rel-win7-gpu-intel

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

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : smoothness.tough_animation_cases
  Metric       : frame_times/css_animations_simultaneous_by_updating_inline_style.html?N_0316

Revision             Result                  N
chromium@510708      16.7 +- 0.306716        21      good
chromium@510723      16.725 +- 0.342994      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=css.animations.simultaneous.by.updating.inline.style.html.N.0316 smoothness.tough_animation_cases

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8964186693438853552


For feedback, file a bug with component Speed>Bisection

1% regression, bisect can't repro, several months old.