You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Material page transition is slow when we enable fade #13736
Specifically, this seems to cause a ~2x regression on the GPU side.
See flutter_gallery__transition_perf average_frame_rasterizer_time_millis around 2017-12-20.
cc @cbracken and @chinmaygarde for the engine side. @abarth was suggesting one trick we could use is noticing that a particular layer hasn't changed from frame to frame and not redrawing it when we change the opacity, or some such; I forget the precise details.
The idea is to be able to cache intermediate layers (in this case the one that gets blended back into the main buffer) rather than just leaves as we do today.
The framework could take each layer with a unique id (similar to the unique id we use for SkPicture). The compositor could then notice with a subtree had the same id as before and consider caching it.
This continues to be our top priority for 1.0; we're not stalled, just working hard. :-)
Reacted by Vid Klopcic, Itay Ganor, Wesley Fantinel and thezjy
Reacted by Carson Holzheimer, Dave Macaulay, Phuc Dam, Luca Romagnoli, Stanislas Signoud, Jake Gough, Paolo Rotolo, Khalifa Visi Islami, Vid Klopcic, Cretezy and 3 more
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.
Activity
Hixie commentedon Jan 18, 2018
Specifically, this seems to cause a ~2x regression on the GPU side.
See flutter_gallery__transition_perf average_frame_rasterizer_time_millis around 2017-12-20.
Hixie commentedon Jan 20, 2018
Here's what it looks like on Nexus 5 today:
MaterialPageRoute.debugEnableFadingRoutes = falseMaterialPageRoute.debugEnableFadingRoutes = trueHixie commentedon Jan 20, 2018
cc @cbracken and @chinmaygarde for the engine side. @abarth was suggesting one trick we could use is noticing that a particular layer hasn't changed from frame to frame and not redrawing it when we change the opacity, or some such; I forget the precise details.
abarth commentedon Jan 20, 2018
The idea is to be able to cache intermediate layers (in this case the one that gets blended back into the main buffer) rather than just leaves as we do today.
The framework could take each layer with a unique id (similar to the unique id we use for SkPicture). The compositor could then notice with a subtree had the same id as before and consider caching it.
70 remaining items
Hixie commentedon Jul 16, 2018
This continues to be our top priority for 1.0; we're not stalled, just working hard. :-)
Remove unnecessary saveLayer (flutter-team-archive#5420)
Hixie commentedon Sep 25, 2018
I'm closing this for now. The remaining work will be tracked in #21756.
github-actions commentedon Sep 1, 2021
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.Remove unnecessary saveLayer (flutter-team-archive/engine#5420)