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

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


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

win-high-dpi

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

=== BISECT JOB RESULTS ===
Perf regression found but unable to continue

Bisect was stopped because a commit couldn't be classified as either
good or bad.


Bisect Details
  Configuration: winx64_high_dpi_perf_bisect
  Benchmark    : smoothness.gpu_rasterization.tough_path_rendering_cases
  Metric       : frame_times/MotionMark Canvas Stroke Shapes

Revision             Result                  N
chromium@494018      63.8806 +- 4.66586      21      good
chromium@494033      64.9443 +- 5.85511      21      unknown
chromium@494047      64.8474 +- 4.41784      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.Canvas.Stroke.Shapes smoothness.gpu_rasterization.tough_path_rendering_cases

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

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


For feedback, file a bug with component Speed>Bisection

Ref build moves too.