New issue
Advanced search Search tips

Issue 651366 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Sep 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

28.5% regression in v8.mobile_infinite_scroll_tbmv2 at 421478:421491

Project Member Reported by ulan@google.com, Sep 29 2016

Issue description

See the link to graphs below.
 

Comment 1 by ulan@google.com, Sep 29 2016

All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=651366

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


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

android-nexus5X

Comment 3 by u...@chromium.org, Sep 29 2016

Status: WontFix (was: Assigned)
This is caused by addition of pinterest website.
Project Member

Comment 4 by 42576172...@developer.gserviceaccount.com, Sep 29 2016

Cc: u...@chromium.org

=== Auto-CCing suspected CL author ulan@chromium.org ===

Hi ulan@chromium.org, the bisect results pointed to your CL below as possibly
causing a regression. Please have a look at this info and see whether
your CL be related.


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


===== SUSPECTED CL(s) =====
Subject : Replace twitter with pinterest in v8.mobile_infinite_scroll_tbmv2.
Author  : ulan
Commit description:
  
The twitter website has small V8 heap (6MB) and doesn't do any major GC.
The pinterest website has larger V8 heap (35MB) and does 6 major GCs.

So for GC team pinterest is more interesting than twitter.

NOTE for perf sheriffs:
Regressions and improvements are expected in mobile_infinite_scroll_tbmv2.

Review-Url: https://codereview.chromium.org/2372433003
Cr-Commit-Position: refs/heads/master@{#421490}
Commit  : bdaa23ddfe686d134e5fa4f55b68910814fa8b03
Date    : Wed Sep 28 10:15:43 2016


===== TESTED REVISIONS =====
Revision         Mean      Std Dev  N  Good?
chromium@421477  33358307  218065   5  good
chromium@421484  33440498  185780   5  good
chromium@421488  33568043  442677   5  good
chromium@421489  33402059  167560   5  good
chromium@421490  42979779  638146   5  bad    <--
chromium@421491  42623079  226357   5  bad

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 651366

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

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/704
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9000193040485428928


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

| 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