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

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


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

chromium-rel-win7-gpu-intel

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

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

Suspected Commit
  Author : Zhenyao Mo
  Commit : 1202f66559ca7e37f643a691cac72144ab60493f
  Date   : Thu Nov 09 00:45:05 2017
  Subject: [reland] Move GPU compositing blacklisting to GPU process.

Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : thread_times.tough_compositor_cases
  Metric       : tasks_per_frame_GPU/tasks_per_frame_GPU

Revision             Result                         N
chromium@514947      0.0 +- 0.0                     6      good
chromium@514999      0.0 +- 0.0                     6      good
chromium@515025      0.0 +- 0.0                     6      good
chromium@515032      0.0 +- 0.0                     6      good
chromium@515035      0.0 +- 0.0                     6      good
chromium@515036      0.00249965 +- 0.000510996      6      bad       <--
chromium@515037      0.00254289 +- 0.000604662      6      bad
chromium@515038      0.00244575 +- 0.000813235      6      bad
chromium@515050      0.00259218 +- 4.66999e-06      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 thread_times.tough_compositor_cases

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

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


For feedback, file a bug with component Speed>Bisection