Issue metadata
Sign in to add a comment
|
Performance validation and improvement tasks for gpu-process display compositor |
||||||||||||||||||||||||
Issue descriptionMoving display compositor out of process is likely to change performance characteristics of the chrome UI. We need to measure these and compare before/after and then making improvements as needed. Tasks that fall out of measuring can be added here as we find them. crbug.com/672303 lists some performance improvements that can be possible with a display compositor in the gpu process, and/or things we could do but never did until now. ⛆ |
|
|
,
Jun 12 2017
,
Jun 12 2017
,
Jun 12 2017
,
Jun 12 2017
ok i lied this isn't a dupe. This is display compositor-specific things. 672303 is general mus things.
,
Jun 12 2017
,
Jun 12 2017
,
Jun 12 2017
,
Jun 12 2017
,
Jun 12 2017
,
Jun 12 2017
,
Nov 21 2017
,
Feb 26 2018
,
Sep 13
Archiving old bugs that haven't been actively assigned in over 180 days. If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks!
,
Sep 13
Archiving old bugs that haven't been actively assigned in over 180 days. If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks!
,
Sep 13
Archiving old bugs that haven't been actively assigned in over 180 days. If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks! |
||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by danakj@chromium.org
, Jun 12 2017Blocking: 601863