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

Issue 636354 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 636360
Owner:
Last visit > 30 days ago
Closed: Aug 2016
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

97.4% regression in memory.long_running_idle_gmail_background_tbmv2 at 410299:410309

Project Member Reported by pmeenan@chromium.org, Aug 10 2016

Issue description

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

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


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

android-nexus7v2
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Aug 10 2016


===== BISECT JOB RESULTS =====
Status: completed


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@410298  49.1044  12.1288  18  good
chromium@410309  47.8059  13.8839  18  bad

Bisect job ran on: android_nexus7_perf_bisect
Bug ID: 636354

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests memory.long_running_idle_gmail_background_tbmv2
Test Metric: v8-gc-scavenger_max/v8-gc-scavenger_max
Relative Change: 5.46%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus7_perf_bisect/builds/3185
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9004710070016379824


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

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

Comment 5 by 42576172...@developer.gserviceaccount.com, Aug 11 2016


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


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@410309  43.9416  5.55441  8  bad

Bisect job ran on: android_nexus7_perf_bisect
Bug ID: 636354

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests memory.long_running_idle_gmail_background_tbmv2
Test Metric: v8-gc-scavenger_max/v8-gc-scavenger_max
Relative Change: 5.96%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus7_perf_bisect/builds/3193
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9004696261581105424


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

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

Comment 7 by 42576172...@developer.gserviceaccount.com, Aug 11 2016


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


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@410309  43.9416  5.55441  8  bad

Bisect job ran on: android_nexus7_perf_bisect
Bug ID: 636354

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests memory.long_running_idle_gmail_background_tbmv2
Test Metric: v8-gc-scavenger_max/v8-gc-scavenger_max
Relative Change: 5.96%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus7_perf_bisect/builds/3193
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9004696261581105424


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

| 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!
Re-kicked with wider range
Project Member

Comment 10 by 42576172...@developer.gserviceaccount.com, Aug 12 2016

Mergedinto: 636360
Status: Duplicate (was: Assigned)

===== BISECT JOB RESULTS =====
Status: completed


===== SUSPECTED CL(s) =====
Subject : Unify memory optimization modes and flags.
Author  : ulan
Commit description:
  
This patch folds --optimize-for-size flag and check for low-memory device
into Heap::ShouldOptimizeForMemoryUsage() predicate.

It has the following side effects:
- the heap growing factor for low-memory devices is capped at 1.3 (old value was 2.0).
- the memory reducer will be more aggressive for low-memory devices.

BUG= chromium:634900 

Review-Url: https://codereview.chromium.org/2218703004
Cr-Commit-Position: refs/heads/master@{#38406}
Commit  : 6cebf7d963c18e2ab09f2320c949baf0a4bed721
Date    : Sun Aug 07 15:36:10 2016


===== TESTED REVISIONS =====
Revision                       Mean     Std Dev  N  Good?
chromium@410289                50.3998  11.4532  8  good
chromium@410310                43.3123  6.83582  8  good
chromium@410320                50.3161  13.7385  8  good
chromium@410323                47.394   9.2852   8  good
chromium@410323,v8@422d14350d  45.5568  4.95519  5  good
chromium@410323,v8@6cebf7d963  84.8816  8.32986  5  bad    <--
chromium@410323,v8@5e685567ea  78.1676  3.56991  5  bad
chromium@410323,v8@265399ed9a  74.0853  11.3027  8  bad
chromium@410324                75.5846  8.03106  8  bad
chromium@410325                79.0899  12.3892  8  bad
chromium@410330                79.4298  10.3453  8  bad
chromium@410370                75.8401  13.7457  8  bad

Bisect job ran on: android_nexus7_perf_bisect
Bug ID: 636354

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests memory.long_running_idle_gmail_background_tbmv2
Test Metric: v8-gc-scavenger_max/v8-gc-scavenger_max
Relative Change: 39.53%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus7_perf_bisect/builds/3200
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9004618521436774016


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

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

Sign in to add a comment