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

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


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

chromium-rel-win10

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

=== BISECT JOB RESULTS ===
Perf regression found but unable to narrow commit range

Build failures prevented the bisect from narrowing the range further.


Bisect Details
  Configuration: winx64_10_perf_bisect
  Benchmark    : kraken
  Metric       : Total/Total
  Change       : 0.62% | 1210.30714286 -> 1205.04285714

Suspected Commit Range
  4 commits in range
  https://chromium.googlesource.com/chromium/src/+log/ef18e39e545a8ea0d22ee8bdf6dd25a76e760b24..defbffe2f169f68088470bf1449481d47ee08374


Revision             Result                  N
chromium@497381      1210.31 +- 17.6088      14       good
chromium@497415      1209.31 +- 15.431       14       good
chromium@497437      1211.12 +- 13.7566      14       good
chromium@497443      1211.42 +- 28.8373      21       good
chromium@497444      1210.2 +- 20.5895       21       good
chromium@497445      ---                     ---      build failure
chromium@497446      ---                     ---      build failure
chromium@497447      ---                     ---      build failure
chromium@497448      1205.04 +- 21.3793      14       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 kraken

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

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


For feedback, file a bug with component Speed>Bisection

Ref also increases at the same time => infra related change.