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

Issue 650620 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Oct 2016
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

2.5%-6.1% regression in memory.top_10_mobile at 419965:420110

Project Member Reported by hpayer@chromium.org, Sep 27 2016

Issue description

See the link to graphs below.
 
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Sep 28 2016


===== BISECT JOB RESULTS =====
Status: failed


===== TESTED REVISIONS =====
Revision                       Mean     Std Dev  N  Good?
chromium@420030                1158874  10040.5  5  good
chromium@420034                1168451  7905.42  4  good
chromium@420036                1170353  17715.3  5  good
chromium@420036,v8@8c87ae9b88  1209406  12218.3  4  bad
chromium@420037                1219945  16244.1  5  bad
chromium@420044                1226570  12004.4  5  bad

Bisect job ran on: android_one_perf_bisect
Bug ID: 650620

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests system_health.memory_mobile
Test Metric: memory:chrome:renderer_processes:reported_by_chrome:v8:heap:code_space:effective_size_avg/memory:chrome:renderer_processes:reported_by_chrome:v8:heap:code_space:effective_size_avg
Relative Change: 5.95%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_one_perf_bisect/builds/1652
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9000367334221692512


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5871329088110592

| 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 Tests>AutoBisect.  Thank you!

===== BISECT JOB RESULTS =====
Status: failed


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@420000  1538263  3747.2   5  good
chromium@420020  1539885  2868.54  5  good
chromium@420025  1538280  4475.84  8  good
chromium@420028  1552939  11283.3  8  bad
chromium@420030  1560254  7751.72  8  bad
chromium@420040  1575419  9149.43  5  bad
chromium@420080  1579411  3447.35  5  bad

Bisect job ran on: android_nexus6_perf_bisect
Bug ID: 650620

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests memory.top_10_mobile
Test Metric: memory:chrome:renderer_processes:reported_by_chrome:v8:heap:code_space:effective_size_avg/memory:chrome:renderer_processes:reported_by_chrome:v8:heap:code_space:effective_size_avg
Relative Change: 2.67%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus6_perf_bisect/builds/2605
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8999658230211817392


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5267110505218048

| 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 Tests>AutoBisect.  Thank you!

Comment 6 by hpayer@chromium.org, Oct 11 2016

Status: WontFix (was: Assigned)
Regression not significant.

Sign in to add a comment