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

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


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

chromium-rel-win7-gpu-nvidia

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

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

Bisect Details
  Configuration: winx64nvidia_perf_bisect
  Benchmark    : smoothness.gpu_rasterization.tough_filters_cases
  Metric       : frame_times/MotionMark Focus

Revision             Result                  N
chromium@509375      34.6492 +- 8.45071      21      good
chromium@509446      35.2528 +- 4.62672      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=MotionMark.Focus smoothness.gpu_rasterization.tough_filters_cases

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

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


For feedback, file a bug with component Speed>Bisection

Chart is pretty noisy and bisect couldn't repro.