New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 719469 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

10.1% regression in system_health.memory_mobile at 469242:469319

Project Member Reported by kraynov@chromium.org, May 8 2017

Issue description

See the link to graphs below.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=719469

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


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

android-nexus6
Mergedinto: 718910
Status: Duplicate (was: Untriaged)

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

Suspected Commit
  Author : alexilin
  Commit : f89e3e140fa7c28737f493a02e7103ab3946a677
  Date   : Thu May 04 13:10:23 2017
  Subject: predictors: Enable SpeculativeResourcePrefetching for fieldtrial testing.

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:java_heap:proportional_resident_size_avg/browse_news/browse_news_qq
  Change       : 6.03% | 22673749.3333 -> 24040106.6667

Revision             Result                  N
chromium@469241      22673749 +- 526226      6      good
chromium@469280      22711979 +- 245669      6      good
chromium@469300      22639616 +- 853050      6      good
chromium@469310      22749525 +- 451431      6      good
chromium@469315      22905856 +- 728167      6      good
chromium@469316      22743381 +- 365471      6      good
chromium@469317      24209067 +- 426040      6      bad       <--
chromium@469319      24040107 +- 587304      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=browse.news.qq system_health.memory_mobile

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

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


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

Suspected Commit
  Author : alexilin
  Commit : f89e3e140fa7c28737f493a02e7103ab3946a677
  Date   : Thu May 04 13:10:23 2017
  Subject: predictors: Enable SpeculativeResourcePrefetching for fieldtrial testing.

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:java_heap:proportional_resident_size_avg/browse_news/browse_news_qq
  Change       : 4.69% | 22764885.3333 -> 23833600.0

Revision             Result                  N
chromium@469241      22764885 +- 572991      6      good
chromium@469280      22780587 +- 716076      6      good
chromium@469300      22695595 +- 531618      6      good
chromium@469310      22777173 +- 655299      6      good
chromium@469315      22748501 +- 208427      6      good
chromium@469316      22872747 +- 584600      6      good
chromium@469317      24080043 +- 435145      6      bad       <--
chromium@469319      23833600 +- 631601      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=browse.news.qq system_health.memory_mobile

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

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


| 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