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

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


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

win-high-dpi

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

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

Bisect Details
  Configuration: winx64_high_dpi_perf_bisect
  Benchmark    : smoothness.tough_canvas_cases
  Metric       : frame_times/tough_canvas_cases_rendering_throughput_canvas_lines.html

Revision             Result                   N
chromium@495290      16.4857 +- 0.274096      21      good
chromium@496774      16.5261 +- 0.314949      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=tough.canvas.cases.rendering.throughput.canvas.lines.html 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/8970275386012875808


For feedback, file a bug with component Speed>Bisection

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

There seems to have been some kind of outage->smaller regression in some of the cases. Other cases have no outage->large regression. The bisect in #3 was the former, kicked off another bisect for the latter.

=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : Brian White
  Commit : 7662ff8cb53121cd4d8916007d430b36efd45895
  Date   : Thu Aug 24 00:03:13 2017
  Subject: Validate histograms before and after each task on Android.

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : smoothness.tough_canvas_cases
  Metric       : frame_times/http___www.smashcat.org_av_canvas_test_
  Change       : 19.13% | 17.6388147853 -> 21.0136624627

Revision             Result                   N
chromium@496667      17.6388 +- 0.460505      6      good
chromium@496809      17.7416 +- 0.325758      6      good
chromium@496845      17.6783 +- 0.255973      6      good
chromium@496863      17.8902 +- 0.425952      6      good
chromium@496872      17.6506 +- 0.360771      6      good
chromium@496876      17.909 +- 0.331245       6      good
chromium@496877      17.7116 +- 0.278927      6      good
chromium@496878      21.0371 +- 0.633275      6      bad       <--
chromium@496880      21.2452 +- 1.07135       6      bad
chromium@496950      21.0137 +- 1.15264       6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=http...www.smashcat.org.av.canvas.test. 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/8970265159744412752


For feedback, file a bug with component Speed>Bisection