New issue
Advanced search Search tips

Issue 832368 link

Starred by 2 users

Issue metadata

Status: Available
Owner: ----
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 1
Type: Bug-Regression
Proj-XR



Sign in to add a comment

1.5%-173.6% regression in xr.browsing.wpr.static at 549885:549964

Project Member Reported by bsheedy@google.com, Apr 12 2018

Issue description

Bisect points to https://chromium-review.googlesource.com/999802. Not familiar with the CL, but looks like we traded performance for a larger memory footprint?
 
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Apr 12 2018

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

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


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

pixel_xl
Components: Internals>VR
Labels: Proj-VR VR-Perf
Yeah, I expected some tiny memory impact, but not this much. What's confusing to me is why this wasn't a constant absolute delta increase. It really shouldn't depend on the page at all.

Also, the memory impact should be very short-lived when changing the size of the content rect. Maybe we're picking up on the short-lived size increase flakily or something...
Labels: -Pri-2 -M-67 M-68 OS-Android Pri-1
I think the tradeoff is worth it for 67, and we should try to do better for 68.
Labels: -M-68 M-69
Components: Internals>XR
Labels: -M-69 Target-70
Removing Internals>VR component and assigning to Internals>XR
Components: -Internals>VR
Owner: ----
Status: Available (was: Assigned)

Sign in to add a comment