New issue
Advanced search Search tips

Issue 826032 link

Starred by 2 users
Status: Fixed
Owner:
cjgrant@chromium.org
Closed: Apr 2018
Cc:
bsheedy@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression
Proj-XR


Show other hotlists

Hotlists containing this issue:
Hotlist-1


Sign in to add a comment

1%-43.2% regression in xr.browsing.wpr.static at 545450:545541

Project Member Reported by bsheedy@google.com, Mar 26 2018 
Various GPU memory and draw_frame regressions occurred as a result of https://chromium-review.googlesource.com/976685.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Mar 26 2018 

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

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


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

pixel_xl

Comment 2 by bsheedy@chromium.org, Mar 26 2018

Components: Internals>VR
Labels: Proj-VR VR-Perf

Comment 3 by cjgrant@chromium.org, Apr 16 2018

Status: Fixed (was: Assigned)
We did a performance audit, and introduced a set of improvements, including:
- Optimizing tree walks
- Rendering improvements to the content (bringing Pixel XL back under budget)
- Centralizing texture rendering code (for truer profiling)

https://docs.google.com/document/d/12rStugbANDECQ_oPFkGOJ9VAOQe6Xm3eGpeQ8iMks7M/edit#

These are general improvements, not specific to this regression, but they serve to address this bug.

Comment 4 by dougman@chromium.org, Apr 16 2018

Labels: Test-Complete

Comment 5 by btebbs@chromium.org, Jul 4

Components: Internals>XR
►

Sign in to add a comment