Surface Synchronization: Avoid unnecessary LocalSurfaceId allocations
LocalSurfaceId allocations are expensive because they force a commit and draw and could increase memory usage. On Android, we were allocating a new parent LocalSurfaceId every time the child LocalSurfaceId changed and blocking UI on the new parent LocalSurfaceId which does not make any sense. Instead, we accept the LocalSurfaceId provided by the child and embed it in the parent. This improves Surface synchronization performance on Android substantially. Before: https://pinpoint-dot-chromeperf.appspot.com/job/14c43963240000 After: https://pinpoint-dot-chromeperf.appspot.com/job/14e7a563240000 Change-Id: I46a85c6d718b97163c371adb169bc4a9d896c68a Reviewed-on: https://chromium-review.googlesource.com/1105019Reviewed-by:Antoine Labour <piman@chromium.org> Reviewed-by:
Saman Sami <samans@chromium.org> Commit-Queue: Fady Samuel <fsamuel@chromium.org> Cr-Commit-Position: refs/heads/master@{#568590}
Showing
Please register or sign in to comment