VR Overflow menu-induced rendering regressions |
||||||
Issue descriptionIt looks like the addition of the VR overflow menu (https://chromium-review.googlesource.com/c/chromium/src/+/967256) caused a number of draw_* and update_* regressions. This is probably unavoidable since we're adding new UI, but it'll be good to double check that. The memory regressions in the same regression range are likely related, but that has yet to be confirmed.
,
Mar 21 2018
,
Mar 22 2018
Memory regressions confirmed to be caused by the overflow menu, as well.
,
Mar 24 2018
As mentioned, I think the regressions aren't regressions, but simply the overhead of adding more UI. I think we should assess where we are with performance (as a whole) after M-67. Right now, it's not an issue (although it's good to have these metrics to catch unnaturally large increases). Changing to M-68.
,
Apr 16 2018
Closing, as per the recent performance scrub. We improved performance in many regards, and should now be less subject to the impact of new (unshown) UI.
,
Apr 16 2018
,
Jul 4
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Mar 21 2018