New issue
Advanced search Search tips

Issue 728947 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 728471
Owner: ----
Closed: Jun 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

5.6%-230.9% regression in v8.browsing_mobile_classic at 475884:475968

Project Member Reported by jgruber@chromium.org, Jun 2 2017

Issue description

Maybe infra-related: refs also regress at the same time.
 

=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:allocated_objects_size_avg/browse_social


Please refer to the following doc on diagnosing memory regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/memory-infra/memory_benchmarks.md

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 system_health.memory_mobile

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

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


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

=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:allocated_objects_size_avg/browse_social


Please refer to the following doc on diagnosing memory regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/memory-infra/memory_benchmarks.md

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 system_health.memory_mobile

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

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


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

=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:allocated_objects_size_avg/browse_social


Please refer to the following doc on diagnosing memory regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/memory-infra/memory_benchmarks.md

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 system_health.memory_mobile

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

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


| 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!
Status: WontFix (was: Untriaged)
Seems to be a combination of issues:
* Both story and associated ref regress on the same range in some cases.
* browse_social regresses since new substories have been added.
* browse_media regresses but recovers.
Mergedinto: 728471
Status: Duplicate (was: WontFix)

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

Suspected Commit
  Author : nednguyen
  Commit : 24245dde6fc83c8881775a3d2556797f5bba287b
  Date   : Wed May 31 11:04:00 2017
  Subject: Always execute network_quiescence.js script upon navigating to a page

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/load_search/load_search_google
  Change       : 3.74% | 4361719.55556 -> 4527944.0

Revision                                 Result                  N
chromium@475867                          4361720 +- 23807.0      9       good
chromium@475884                          4378420 +- 97239.7      9       good
chromium@475893                          4371828 +- 37702.7      9       good
chromium@475897                          4377650 +- 101383       14      good
chromium@475897,catapult@24245dde6f      4500013 +- 111159       6       bad       <--
chromium@475898                          4464962 +- 208363       9       bad
chromium@475899                          4509519 +- 174607       6       bad
chromium@475901                          4454863 +- 190054       9       bad
chromium@475934                          4527944 +- 58738.2      6       bad

Please refer to the following doc on diagnosing memory regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/memory-infra/memory_benchmarks.md

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=load.search.google system_health.memory_mobile

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

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


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

=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg/background_search


Please refer to the following doc on diagnosing memory regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/memory-infra/memory_benchmarks.md

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 system_health.memory_mobile

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

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


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

=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : v8.browsing_mobile
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg/browse_social


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 v8.browsing_mobile

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

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


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

=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:allocated_objects_size_avg/browse_social


Please refer to the following doc on diagnosing memory regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/memory-infra/memory_benchmarks.md

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 system_health.memory_mobile

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

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


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

=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg/background_search


Please refer to the following doc on diagnosing memory regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/memory-infra/memory_benchmarks.md

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 system_health.memory_mobile

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

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


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

=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : v8.browsing_mobile
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg/browse_social


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 v8.browsing_mobile

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

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


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

Sign in to add a comment