Repository navigation
Flow should optimize away render target switches when the same effect can be achieved via paint options. #9480
Description
Render target switches caused by SkCanvas::saveLayer are expensive on lower end devices. These are typically introduced by flow when there is an opacity layer or clip. However, there are many cases where only a single item (such as an image at a custom opacity) is rendered in this target. In such cases, the paint options (such as one expressing the opacity of the image) can be used to achieve the same effect.
flow should look for such optimizations.
Activity
Hixie commentedon Mar 3, 2020
cc @liyuqian @chinmaygarde is this still relevant?
chinmaygarde commentedon Mar 3, 2020
While there has been progress made on eliding render target switches introduced by the engine itself, there is a lot more to be done on this front. Currently, the opaqueness of the SkPicture presented to the engine hinders its capability to determine if the operation is a group opacity. We should be be able to affect such optimizations once we move to our picture format. Till then, this issue should be kept open.
liyuqian commentedon Mar 4, 2020
@chinmaygarde : is there an issue that tracks the creation of our own picture format? The last news I knew is that Skia sent us a link to SkLiteDL.h
dnfield commentedon Nov 8, 2021
Deduping this against #92874 which is more up to date now
github-actions commentedon Nov 22, 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.