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

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


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

chromium-rel-win7-gpu-intel

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

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

Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : thread_times.tough_scrolling_cases
  Metric       : thread_raster_cpu_time_per_frame/canvas_30000_pixels_per_second

Revision             Result                     N
chromium@495793      0.358088 +- 0.105463       21      good
chromium@495808      0.362588 +- 0.0799991      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=canvas.30000.pixels.per.second thread_times.tough_scrolling_cases

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

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


For feedback, file a bug with component Speed>Bisection

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

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

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

This is pretty widespread, although some of the graphs go up and down. Kicked off bisects on a few different graphs.

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

Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : thread_times.tough_scrolling_cases
  Metric       : thread_raster_cpu_time_per_frame/text_hover_30000_pixels_per_second

Revision             Result                    N
chromium@495793      0.404334 +- 0.175975      21      good
chromium@495808      0.418184 +- 0.164878      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=text.hover.30000.pixels.per.second thread_times.tough_scrolling_cases

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

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


For feedback, file a bug with component Speed>Bisection

=== Auto-CCing suspected CL author thakis@chromium.org ===

Hi thakis@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


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

Suspected Commit
  Author : Nico Weber
  Commit : 7cd2f6bd73c6a9c6200704e995b18ebb3168ead6
  Date   : Sat Aug 19 04:23:54 2017
  Subject: win: Turn off clang-by-default again for now.

Bisect Details
  Configuration: win_perf_bisect
  Benchmark    : thread_times.tough_scrolling_cases
  Metric       : thread_total_all_cpu_time_per_frame/text_10000_pixels_per_second
  Change       : 1.26% | 16.769011053 -> 16.9803615902

Revision             Result                   N
chromium@495791      16.769 +- 0.39075        9       good
chromium@495800      16.772 +- 0.556522       14      good
chromium@495801      16.7019 +- 0.293662      6       good
chromium@495802      17.0828 +- 0.305172      6       bad       <--
chromium@495804      17.0344 +- 0.237226      6       bad
chromium@495808      16.9804 +- 0.313973      9       bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=text.10000.pixels.per.second thread_times.tough_scrolling_cases

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

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


For feedback, file a bug with component Speed>Bisection

=== Auto-CCing suspected CL author dschuyler@chromium.org ===

Hi dschuyler@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


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

Suspected Commit
  Author : Dave Schuyler
  Commit : 8aa2bf834647e8f2e5f97f8b0e9cc98cb727d44a
  Date   : Sat Aug 19 02:50:52 2017
  Subject: [MD settings] settings-toggle-button default to settings-box styling

Bisect Details
  Configuration: win_perf_bisect
  Benchmark    : thread_times.tough_scrolling_cases
  Metric       : thread_total_all_cpu_time_per_frame/text_30000_pixels_per_second
  Change       : 2.54% | 33.4180134745 -> 34.2678304206

Revision             Result                   N
chromium@495791      33.418 +- 1.31862        9       good
chromium@495792      34.2531 +- 1.30818       9       bad       <--
chromium@495793      34.1607 +- 0.946555      6       bad
chromium@495794      34.5 +- 1.15197          6       bad
chromium@495796      34.68 +- 1.81342         6       bad
chromium@495800      34.4932 +- 2.26765       14      bad
chromium@495808      34.2678 +- 1.96068       9       bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=text.30000.pixels.per.second thread_times.tough_scrolling_cases

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

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


For feedback, file a bug with component Speed>Bisection

Sorry dschulyer, I think the bisect in #10 must have just randomly gotten a low result in its first run, this seems unlikely to be your CL.

thakis, I think these probably go up and down because they regress when we turn off clang-by-default. WontFix?

 Issue 760160  has been merged into this issue.

 Issue 760160  has been merged into this issue.