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

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


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

chromium-rel-win7-gpu-intel

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

Suspected Commit
  Author : Hans Wennborg
  Commit : d2c91228a51bdf37ae3b2e501fb53c0528f1629c
  Date   : Fri Jul 28 20:11:05 2017
  Subject: win: Set is_clang=true by default

Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : speedometer2
  Metric       : EmberJS-TodoMVC/Speedometer2
  Change       : 5.15% | 1443.31427778 -> 1517.67305556

Revision             Result                  N
chromium@490421      1443.31 +- 100.744      9      good
chromium@490459      1455.71 +- 179.913      9      good
chromium@490478      1439.61 +- 12.9934      6      good
chromium@490488      1440.71 +- 24.5386      6      good
chromium@490493      1457.54 +- 75.1388      9      good
chromium@490494      1536.21 +- 23.7984      6      bad       <--
chromium@490495      1520.73 +- 123.742      9      bad
chromium@490497      1517.67 +- 131.548      9      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=Speedometer2 speedometer2

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

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


For feedback, file a bug with component Speed>Bisection

Wrong dupe