New issue
Advanced search Search tips

Issue 857212 link

Starred by 2 users
Status: WontFix
Owner:
fmalita@chromium.org
Closed: Jun 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression
Proj-XR
Proj-XR-VR



Sign in to add a comment

1.4%-3.7% regression in xr.browsing.wpr.static at 570371:570406

Project Member Reported by bsheedy@google.com, Jun 27 2018 
Bisect points to https://chromium-review.googlesource.com/1113661 as the culprit. Not sure if this is expected or something we should worry about.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Jun 27 2018 

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

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


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

pixel_xl

Comment 2 by bsheedy@chromium.org, Jun 27 2018

Components: UI>Browser>VR
Labels: Proj-VR VR-Perf

Comment 3 by fmalita@chromium.org, Jun 28 2018

Status: WontFix (was: Assigned)
I believe these are expected: we stopped splitting certain types of SharedBuffers into 4KB segments and instead we allocate a single contiguous slab.

These metrics appear to track average allocation size, which obviously went up when we switched from a bunch of 4KB allocations to a single large one:

partition_alloc:allocated_objects_size_avg
partition_alloc:effective_size_avg
►

Sign in to add a comment