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

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


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

chromium-rel-win7-gpu-nvidia

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

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

Bisect Details
  Configuration: winx64nvidia_perf_bisect
  Benchmark    : smoothness.tough_animation_cases
  Metric       : frame_times/overlay_background_color_css_transitions.html

Revision             Result                  N
chromium@495217      299.893 +- 49.3799      21      good
chromium@495343      302.222 +- 62.7437      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=overlay.background.color.css.transitions.html 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/8970001251904081328


For feedback, file a bug with component Speed>Bisection

Metric seems bimodal.