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

Issue 677401 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 675551
Owner: ----
Closed: Dec 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

5.1% regression in system_health.memory_mobile at 439295:439330

Project Member Reported by alexclarke@chromium.org, Dec 29 2016

Issue description

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

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


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

android-nexus6
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Dec 29 2016

Mergedinto: 675551
Status: Duplicate (was: Untriaged)

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


===== SUSPECTED CL(s) =====
Subject : [heap] Reland "Use RAIL mode for initial heap sizing".
Author  : ulan
Commit description:
  
The original patch was reverted because of performance
regressions caused by removal of old heap sizing heuristics.

This patch keeps the old heuristics and adds RAIL mode.

BUG= chromium:613518 

Review-Url: https://codereview.chromium.org/2576543002
Cr-Commit-Position: refs/heads/master@{#41773}
Commit  : 7bdb906946b94e9ba10de13e104a39bbcabedbd6
Date    : Fri Dec 16 16:59:44 2016


===== TESTED REVISIONS =====
Revision                       Mean      Std Dev  N   Good?
chromium@439294                10339800  526492   9   good
chromium@439303                10313619  552671   14  good
chromium@439308                10336368  970230   21  good
chromium@439309                10306785  487976   9   good
chromium@439309,v8@3f5a60ac17  10265059  453563   14  good
chromium@439309,v8@b2b5d0ab5b  10348450  777021   21  good
chromium@439309,v8@7bdb906946  10593142  151951   14  bad    <--
chromium@439310                10579220  149220   9   bad
chromium@439312                10612365  87423.7  14  bad
chromium@439330                10587688  143036   9   bad

Bisect job ran on: android_nexus6_perf_bisect
Bug ID: 677401

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.social.instagram system_health.memory_mobile
Test Metric: memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/load_social/load_social_instagram
Relative Change: 2.40%

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


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

| 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