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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgrM2RpgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgrPPJogkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgrL2JtwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgrL3CuwkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgrP-c-QgM


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

android-nexus5
android-nexus6
android-nexus7v2
android-webview-nexus6

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

=== Auto-CCing suspected CL author verwaest@chromium.org ===

Hi verwaest@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


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

Suspected Commit
  Author : Toon Verwaest
  Commit : 810e8593003c33c058cee7ad0fcd42c788cb5597
  Date   : Fri Mar 24 10:40:49 2017
  Subject: [ic] Make sure we don't use a smi-handler for FunctionTemplate getters

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : V8 C++:duration_avg/browse_news/browse_news_qq
  Change       : 13.44% | 1161.9945 -> 1318.12233333

Revision                           Result                  N
chromium@459484                    1161.99 +- 39.4728      6      good
chromium@459487                    1151.44 +- 94.8465      6      good
chromium@459488                    1182.59 +- 59.6184      6      good
chromium@459488,v8@c152d45950      1144.81 +- 110.728      6      good
chromium@459488,v8@b7ac3668ea      1162.14 +- 108.405      9      good
chromium@459488,v8@810e859300      1274.42 +- 113.869      6      bad       <--
chromium@459488,v8@69e02958d3      1323.69 +- 69.5669      6      bad
chromium@459488,v8@f12b193df9      1317.57 +- 114.265      6      bad
chromium@459489                    1303.58 +- 55.9867      6      bad
chromium@459490                    1314.78 +- 124.63       6      bad
chromium@459496                    1316.26 +- 98.3614      6      bad
chromium@459507                    1271.14 +- 62.8257      6      bad
chromium@459529                    1316.16 +- 45.4293      6      bad
chromium@459573                    1318.12 +- 55.8125      6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.news.qq v8.runtimestats.browsing_mobile

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

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


| 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!

The indicated CL was a perf regression fix itself. Over time we'll make everything data driven so we may restore this later.