New issue
Advanced search Search tips

Issue 913442 link

Starred by 2 users
Status: Duplicate
Owner:
u...@chromium.org
Closed: Dec 12
Cc:
petermarshall@google.com
u...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

9.2%-113.1% regression in v8.browsing_desktop at 613995:614208

Project Member Reported by petermarshall@google.com, Dec 10 
See the link to graphs below.
Project Member

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

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

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


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

Win 7 Nvidia GPU Perf
linux-perf

v8.browsing_desktop - Benchmark documentation link:
  None
Project Member

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

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/1453eb16140000

Do not pretenure descriptor arrays. by ulan@chromium.org
https://chromium.googlesource.com/v8/v8/+/92e228534a472c5ff55f7ed536f5c6ba7daccedb
v8-gc-scavenger: 2.138 → 4 (+1.863)

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

Benchmark documentation link:
  None

Comment 4 by u...@chromium.org, Dec 12

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

Sign in to add a comment