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

Issue 677402 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

131.1% regression in memory.long_running_idle_gmail_background_tbmv2 at 439503:439596

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=677402

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


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

chromium-rel-mac10
Project Member

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

Mergedinto: 676550
Status: Duplicate (was: Untriaged)

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


===== SUSPECTED CL(s) =====
Subject : [heap] Use RAIL mode for starting incremental marking.
Author  : ulan
Commit description:
  
This patch delays start of incremental marking during L phase of RAIL
and adjusts ShouldOptimizeForLoadTime to check allocation limit.

BUG= chromium:613518 

Review-Url: https://codereview.chromium.org/2583033003
Cr-Commit-Position: refs/heads/master@{#41797}
Commit  : 039e29f7505cf75d27d7681fab51d50f53dcc7bd
Date    : Mon Dec 19 11:34:34 2016


===== TESTED REVISIONS =====
Revision                       Mean     Std Dev   N  Good?
chromium@439502                2.5905   1.86608   6  good
chromium@439549                2.74317  1.66851   6  good
chromium@439561                2.5205   1.8963    6  good
chromium@439567                2.23833  0.954168  6  good
chromium@439570                2.46689  2.43988   9  good
chromium@439571                2.524    1.50107   6  good
chromium@439571,v8@81dd9847cf  2.69083  2.18244   6  good
chromium@439571,v8@58247e87be  2.27217  0.994544  6  good
chromium@439571,v8@039e29f750  5.304    1.16163   6  bad    <--
chromium@439571,v8@52702e55aa  5.67833  1.34752   6  bad
chromium@439571,v8@8ac9e55aa6  5.584    1.8687    6  bad
chromium@439572                4.97483  1.24531   6  bad
chromium@439573                5.4302   1.5453    5  bad
chromium@439596                5.04117  1.28758   6  bad

Bisect job ran on: mac_10_10_perf_bisect
Bug ID: 677402

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests memory.long_running_idle_gmail_background_tbmv2
Test Metric: v8-gc-incremental-step_max/v8-gc-incremental-step_max
Relative Change: 94.60%

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_10_10_perf_bisect/builds/2522
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8991949370810088160


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

| 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