New issue
Advanced search Search tips

Issue 729246 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Jun 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

4.8% regression in memory.top_10_mobile at 474976:475086

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

Issue description

See the link to graphs below.
 

Comment 1 by m...@chromium.org, Jun 2 2017

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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgptqlsAoM


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

android-nexus5

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

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:gpu_memory:proportional_resident_size_avg/foreground/http_m_intl_taobao_com_group_purchase_html

Revision             Result                    N
chromium@474975      67856677 +- 16128965      21      good
chromium@475086      71530984 +- 16507335      21      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 memory.top_10_mobile

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

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


| 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 ===
NO Perf regression found

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:gpu_memory:proportional_resident_size_avg/foreground/http_m_intl_taobao_com_group_purchase_html

Revision             Result                    N
chromium@474975      66965699 +- 12761407      21      good
chromium@475086      70378057 +- 18067717      21      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 memory.top_10_mobile

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

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


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

Comment 6 by m...@chromium.org, Jun 5 2017

Status: WontFix (was: Untriaged)
Seems to be normal when looking at longer-term view. Noisy metric.

Sign in to add a comment