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

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


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

android-nexus5
android-nexus7v2

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

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

Hi ksakamoto@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 : Kunihiko Sakamoto
  Commit : a604b6e8d467a2c9a9dc134b1ca6f729b410052f
  Date   : Wed Aug 16 16:22:39 2017
  Subject: ResourceLoadScheduler: add the memory stats feature to fieldtrial test config

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : Total:duration_avg/browse_social/browse_social_facebook_infinite_scroll
  Change       : 16.48% | 31523.0195 -> 36718.6446667

Revision             Result                  N
chromium@494757      31523.0 +- 1386.45      6      good
chromium@494803      31440.3 +- 1741.47      6      good
chromium@494809      31506.5 +- 2582.62      6      good
chromium@494810      36277.2 +- 1462.52      6      bad       <--
chromium@494811      36214.6 +- 1215.9       6      bad
chromium@494812      36850.5 +- 1495.38      6      bad
chromium@494815      36420.3 +- 1085.43      6      bad
chromium@494826      36384.7 +- 1129.72      6      bad
chromium@494848      36904.7 +- 1655.05      6      bad
chromium@494938      36241.0 +- 1866.97      6      bad
chromium@495119      36718.6 +- 1468.24      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.social.facebook.infinite.scroll v8.runtimestats.browsing_mobile

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

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


For feedback, file a bug with component Speed>Bisection

I'm not able to reproduce this locally. This looks like device dependent - I don't see corresponding change in nexus5x / nexus6 graphs.

Note that my CL is just for short-term metrics collection, and the code will go away once we wrap up the ResourceLoadScheduler experiment.

Let me close this, as we will not "launch" this change.

 Issue 759605  has been merged into this issue.

 Issue 759656  has been merged into this issue.

 Issue 760143  has been merged into this issue.

 Issue 761232  has been merged into this issue.