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

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


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

win-high-dpi

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

 Issue 748083  has been merged into this issue.
 Issue 748084  has been merged into this issue.
 Issue 748085  has been merged into this issue.

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

Bisect Details
  Configuration: winx64_high_dpi_perf_bisect
  Benchmark    : media.tough_video_cases_tbmv2
  Metric       : story:power_avg/video.html?src_tulip2.mp3_type_audio

Revision             Result                     N
chromium@487915      0.445674 +- 0.113728       20      good
chromium@488051      0.439238 +- 0.0372997      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=video.html.src.tulip2.mp3.type.audio media.tough_video_cases_tbmv2

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

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


For feedback, file a bug with component Speed>Bisection

Bisect didn't find a culprit, and now the regression is stale.