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

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


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

win-high-dpi

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

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

Suspected Commit
  Author : Khushal
  Commit : ca2c1cf2d9748d25050bfe7f71ee40463588a6a9
  Date   : Thu Jul 27 23:06:43 2017
  Subject: cc: Split pending tree duration metrics based on main/impl side tree.

Bisect Details
  Configuration: winx64_high_dpi_perf_bisect
  Benchmark    : scheduler.tough_scheduling_cases
  Metric       : mean_main_thread_scroll_latency/mean_main_thread_scroll_latency
  Change       : 29.06% | 7.71816666667 -> 5.47533333333

Revision             Result                   N
chromium@490004      7.71817 +- 0.934999      6      good
chromium@490057      8.04217 +- 0.671307      6      good
chromium@490061      8.08217 +- 0.311408      6      good
chromium@490062      7.6825 +- 1.61196        6      good
chromium@490063      5.47733 +- 0.939725      6      bad       <--
chromium@490064      5.5425 +- 0.411485       6      bad
chromium@490071      5.63267 +- 0.955761      6      bad
chromium@490084      5.50717 +- 0.798796      6      bad
chromium@490110      5.47533 +- 0.822779      6      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 scheduler.tough_scheduling_cases

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

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


For feedback, file a bug with component Speed>Bisection