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

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


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

win-high-dpi

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

=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: winx64_high_dpi_perf_bisect
  Benchmark    : smoothness.tough_animation_cases
  Metric       : frame_times/frame_times


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 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/8974256678745019008


For feedback, file a bug with component Speed>Bisection

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

The first bisect timed out because we were trying to run all the pages in the set. I updated the monitoring so this won't happen again. It looks like balls_css_transition_40_properties.html is one of the pages that regressed, and the graph is pretty choppy, so I kicked off a bisect on that one on a wider revision range.

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

Bisect Details
  Configuration: winx64_high_dpi_perf_bisect
  Benchmark    : smoothness.tough_animation_cases
  Metric       : frame_times/balls_css_transition_40_properties.html

Revision             Result                  N
chromium@482193      26.5294 +- 1.96745      21      good
chromium@482889      26.8537 +- 3.87214      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=balls.css.transition.40.properties.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/8973425120372815232


For feedback, file a bug with component Speed>Bisection

Looks like this has recovered as of r484855.