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

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


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

chromium-rel-win7-gpu-intel

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

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

Suspected Commit
  Author : Hans Wennborg
  Commit : 22525134c75ca2a005997a717f6887a23af86210
  Date   : Mon Oct 23 17:10:25 2017
  Subject: win: Re-enable Clang by default

Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : blink_perf.svg
  Metric       : SvgHitTesting/SvgHitTesting
  Change       : 9.23% | 52.9918333333 -> 57.881

Revision             Result                   N
chromium@510764      52.9918 +- 1.18228       6      good
chromium@510794      53.8088 +- 0.748446      6      good
chromium@510809      53.7375 +- 1.79728       6      good
chromium@510817      53.7385 +- 1.69842       6      good
chromium@510821      53.4562 +- 2.17014       6      good
chromium@510823      54.5232 +- 3.89308       6      good
chromium@510824      57.881 +- 2.45599        6      bad       <--

Please refer to the following doc on diagnosing blink_perf regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/speed/benchmark_harnesses/blink_perf.md

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 blink_perf.svg

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

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


For feedback, file a bug with component Speed>Bisection