New issue
Advanced search Search tips

Issue 914797 link

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



Sign in to add a comment

54.1% regression in v8.browsing_desktop at 614702:614965

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

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


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

Win 7 Nvidia GPU Perf

v8.browsing_desktop - Benchmark documentation link:
  None
Project Member

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

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

[heap] Improve incremental steps on allocation by mlippautz@chromium.org
https://chromium.googlesource.com/v8/v8/+/72806449de1bfcb61ebee0bdc30d9e3115413495
v8-gc-incremental-step: 0.4611 → 0.6046 (+0.1435)

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

Benchmark documentation link:
  None

Comment 4 by mlippautz@chromium.org, Dec 20

Cc: -mlippautz@chromium.org
Status: WontFix (was: Assigned)
Tradeoff where we do more work during incremental steps where we call out to the embedder.
►

Sign in to add a comment