New issue
Advanced search Search tips

Issue 916459 link

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



Sign in to add a comment

21%-36.6% regression in v8.browsing_desktop at 614702:614965

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

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

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

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


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

Win 7 Nvidia GPU Perf

v8.browsing_desktop - Benchmark documentation link:
  None

Comment 3 by mlippautz@chromium.org, Dec 20

Status: WontFix (was: Untriaged)
Likely 
  7280644 [heap] Improve incremental steps on allocation by Michael Lippautz · 13 days ago

which is trading of making progress vs avg step size.
Project Member

Comment 4 by 42576172...@developer.gserviceaccount.com, Dec 21 

📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/143c1ee6140000

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

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

Benchmark documentation link:
  None
►

Sign in to add a comment