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

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


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

android-nexus7v2

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

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : v8-gc-full-mark-compactor_max/browse_media/browse_media_imgur

Revision             Result                  N
chromium@490659      68.4684 +- 15.4802      21      good
chromium@490675      65.9266 +- 18.4296      21      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.media.imgur 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/8972265506885671488


For feedback, file a bug with component Speed>Bisection

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

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

Suspected Commit
  Author : Ulan Degenbaev
  Commit : 774a4c5e240569b551cc9d19ae8cac146891d4c4
  Date   : Fri Jul 28 19:42:31 2017
  Subject: Revert "[heap] Reland "[heap] Allow a minimum semi-space size of 512K.""

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : v8-gc-scavenger_max/browse_news/browse_news_qq
  Change       : 30.34% | 6.36416666667 -> 8.29516666667

Revision                           Result                   N
chromium@490643                    6.36417 +- 1.80076       6      good
chromium@490651                    6.3124 +- 0.593866       5      good
chromium@490652                    5.49967 +- 1.03786       6      good
chromium@490652,v8@59ddd6061c      6.355 +- 0.725456        6      good
chromium@490652,v8@e567dd3ab4      5.95417 +- 0.711027      6      good
chromium@490652,v8@774a4c5e24      8.91317 +- 2.25051       6      bad       <--
chromium@490652,v8@4a9718c777      8.62267 +- 1.17587       6      bad
chromium@490653                    8.82117 +- 2.35246       6      bad
chromium@490655                    10.2098 +- 3.12948       6      bad
chromium@490659                    9.43033 +- 2.51541       6      bad
chromium@490675                    8.29517 +- 0.937214      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

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

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


For feedback, file a bug with component Speed>Bisection