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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDguMTYvgkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg2JvTsAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDguOi5ugoM


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

chromium-rel-mac11-pro
chromium-rel-win7-gpu-ati

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

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

Suspected Commit
  Author : yosin
  Commit : 157413286770a7ac5a24c446a30c08f749738276
  Date   : Mon Feb 13 10:55:13 2017
  Subject: Make FrameSelection to hold non-canonicalized DOM positions

Bisect Details
  Configuration: mac_pro_perf_bisect
  Benchmark    : blink_perf.bindings
  Metric       : insert-before/insert-before
  Change       : 10.99% | 49.05099079 -> 43.658831033

Revision             Result                   N
chromium@449918      49.051 +- 1.6388         6      good
chromium@449927      48.9327 +- 1.14321       8      good
chromium@449928      43.7433 +- 0.909078      6      bad       <--
chromium@449929      43.58 +- 0.90418         6      bad
chromium@449930      43.5512 +- 0.795243      5      bad
chromium@449932      43.5507 +- 1.09308       6      bad
chromium@449936      43.6588 +- 0.928444      5      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 blink_perf.bindings

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8987514576722444400

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5608132190928896


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!