-
Notifications
You must be signed in to change notification settings - Fork 28.7k
Clip fix regressed Impeller raster times on Android #114021
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
|
Is clipping on Android with impeller enabled particularly slow? @chinmaygarde I notice there don't seem to be any iOS or non-impeller regressions so I'm inclined to keep this for now... |
Yeah, if #113770 fixed a real bug, we should keep it. I opened this issue so that we can track that the benchmark recovers as we make progress on the backend for Android. |
No, clips should be "free" with the stencil buffers already being present. Perhaps we aren't clearing the render target correctly after the clip causing a load? Should become apparent after profiling. We can keep this open till we get to Android performance. Can we also add a note about the device here this happens on please? |
It looks like the benchmark recovered, at some point, so I'll close this. |
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 |
The fix here #113770 regressed the raster times of the
list_text_layout_impeller_perf__e2e_summary
benchmark:https://flutter-flutter-perf.skia.org/e/?begin=1666280999&end=1666307527&keys=X4dfec7919bc8bf5ff16c3a0b23e31e3d&num_commits=50&request_type=1&xbaroffset=31668
@jonahwilliams @dnfield @iskakaushik
The text was updated successfully, but these errors were encountered: