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

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


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

chromium-rel-win7-dual

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

=== 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    : dromaeo.domcoremodify
  Metric       : dom/dom
  Change       : 3.34% | 721.985358005 -> 697.861844637

Revision             Result                  N
chromium@495791      721.985 +- 6.97524      6      good
chromium@495800      721.439 +- 5.30891      6      good
chromium@495801      724.663 +- 12.8699      6      good
chromium@495802      699.77 +- 15.4103       6      bad       <--
chromium@495804      692.65 +- 6.51774       6      bad
chromium@495808      697.862 +- 16.9129      6      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 dromaeo.domcoremodify

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

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


For feedback, file a bug with component Speed>Bisection