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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgnqSbrAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgnqKCxwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg7rPE8QsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg7rmq9QoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgnsH_ugsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg7uD7zggM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg7smylAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg7v22tAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg7u3D9ggM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg7vPB6gsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg7pa86wgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgrrfn4goM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg7v71jQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg7o-kvAsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg7rj8qQgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg7tKn5wgM


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

android-webview-nexus5X
chromium-rel-mac11
chromium-rel-mac11-air
chromium-rel-win10

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

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

Hi kochi@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 : Takayoshi Kochi
  Commit : fa75e2abb23205caa6d7f61edc89e672e83f6089
  Date   : Wed Jun 28 08:22:13 2017
  Subject: Revert of Relanding [Android] Adding Smart GO/NEXT feature in Chrome (patchset #4 id:80001 of https://codereview.chromium.org/2948593002/ )

Bisect Details
  Configuration: mac_air_perf_bisect
  Benchmark    : v8.runtimestats.browsing_desktop
  Metric       : V8 C++:duration_avg/browse_social/browse_social_facebook_infinite_scroll
  Change       : 60.58% | 1652.65583333 -> 2653.91133333

Revision             Result                  N
chromium@482843      1652.66 +- 65.404       6      good
chromium@482882      1656.97 +- 109.139      6      good
chromium@482901      1652.99 +- 107.125      6      good
chromium@482911      1676.77 +- 78.7367      6      good
chromium@482916      1684.6 +- 197.46        6      good
chromium@482917      1668.42 +- 184.035      6      good
chromium@482918      2705.67 +- 97.8649      6      bad       <--
chromium@482920      2653.91 +- 110.348      6      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 --story-filter=browse.social.facebook.infinite.scroll v8.runtimestats.browsing_desktop

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

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


For feedback, file a bug with component Speed>Bisection

Hmm, this CL was a revert CL that should have fixed  crbug.com/737388  ...

 Issue 737663  has been merged into this issue.

The original CL, by ajith.v landed at 481868
https://codereview.chromium.org/2948593002
and then reverted by me.  The original CL caused some regression
( issue 737388 ) but also got some *progression* - and reverting it was
detected as regression, it seems (see the graph in comment #1).

My revert change just reverted to the original performance, thus
no action can be taken for this issue.  Closing.