New issue
Advanced search Search tips

Issue 916447 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

17.9% regression in v8.browsing_desktop at 617442:617478

Project Member Reported by mlippautz@chromium.org, Dec 19

Issue description

See the link to graphs below.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=916447

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


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

mac-10_13_laptop_high_end-perf

v8.browsing_desktop - Benchmark documentation link:
  None
Cc: keishi@chromium.org
Owner: keishi@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/1001312a140000

Oilpan: Enable HeapCompaction for incremental marking by keishi@chromium.org
https://chromium.googlesource.com/chromium/src/+/b77e6c51c6ac67a51dd55731d220f658bc96f7cc
memory:chrome:renderer_processes:reported_by_chrome:v8:heap:allocated_objects_size: 1.507e+07 → 1.693e+07 (+1.862e+06)

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

Benchmark documentation link:
  None

Sign in to add a comment