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

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


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

linux-release

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

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

Bisect Details
  Configuration: linux_perf_bisect
  Benchmark    : smoothness.tough_canvas_cases
  Metric       : frame_times/tough_canvas_cases_canvas2d_balls_common_bouncing_balls.html?ball_image_with_shadow_back_image

Revision             Result                  N
chromium@464556      478.141 +- 465.275      21      good
chromium@464655      483.491 +- 321.413      19      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=tough.canvas.cases.canvas2d.balls.common.bouncing.balls.html.ball.image.with.shadow.back.image smoothness.tough_canvas_cases

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

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


For feedback, file a bug with component Speed>Bisection

Bisect can't repro, and this went back down (graph that didn't go down only shows ref build)