New issue
Advanced search Search tips

Issue 914791 link

Starred by 1 user
Status: Duplicate
Owner:
u...@chromium.org
Closed: Dec 20
Cc:
petermarshall@chromium.org
u...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

25.9%-37.7% regression in v8.browsing_desktop at 613995:614285

Project Member Reported by petermarshall@chromium.org, Dec 13 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Dec 13 

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

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


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

Win 7 Nvidia GPU Perf
Win 7 Perf

v8.browsing_desktop - Benchmark documentation link:
  None
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Dec 20

Cc: u...@chromium.org
Owner: u...@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/1480378e140000

Do not pretenure descriptor arrays. by ulan@chromium.org
https://chromium.googlesource.com/v8/v8/+/92e228534a472c5ff55f7ed536f5c6ba7daccedb
memory:chrome:renderer_processes:reported_by_chrome:v8:heap:allocated_objects_size: 3.618e+07 → 4.629e+07 (+1.011e+07)

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

Benchmark documentation link:
  None

Comment 4 by petermarshall@chromium.org, Dec 20

Mergedinto: 913482
Status: Duplicate (was: Assigned)
►

Sign in to add a comment