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

Issue 880390 link

Starred by 1 user
Status: Untriaged
Owner: ----
Cc:
maxlg@chromium.org
█ rfbpb@google.com
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

551.6% regression in rendering.mobile at 587034:587067

Project Member Reported by maxlg@chromium.org, Sep 4 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Sep 4 

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

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=3ad2db171f2f1a372426c3949cb3317eb0539ac0ac5f342c07f72ebfead22d97


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

android-nexus5x-perf

rendering.mobile - Benchmark documentation link:
  https://bit.ly/rendering-benchmarks

Comment 3 by maxlg@chromium.org, Sep 4 

Looks like the regression has been fixed.
Project Member

Comment 4 by 42576172...@developer.gserviceaccount.com, Sep 5

Cc: rfbpb@google.com
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/1328bd1b640000

Reland "[heap] Attempt to incorporate backing store counters into heap sizing and GC trigger stragery." by rfbpb@google.com
https://chromium.googlesource.com/v8/v8/+/eb164dbd0066a0078e58932563eeb5fdd2b8e6d6
0.295 → 1.707 (+1.412)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions

Comment 5 by benhenry@google.com, Jan 11

Status: Untriaged (was: Assigned)
Assigned, but no owner or component? Please find a component and/or owner
►

Sign in to add a comment