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

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


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

chromium-rel-mac-retina
chromium-rel-mac11
chromium-rel-mac11-pro
win-high-dpi

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

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

Bisect Details
  Configuration: winx64_high_dpi_perf_bisect
  Benchmark    : media.tough_video_cases_tbmv2
  Metric       : cpu_time_percentage_avg/video.html?src_tulip2.mp3_type_audio_seek

Revision             Result                     N
chromium@494018      0.340952 +- 0.0754743      21      good
chromium@494047      0.345937 +- 0.0570219      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.seek 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/8970675905455381904


For feedback, file a bug with component Speed>Bisection