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
[Impeller] Improve Impeller performance on Vulkan devices without lazily allocated memory support. #144617
The primary trick here is making sure that the transient attachments for the onscreen (MSAA and Depth/Stencil) are effectively recycled. In fact, I think we can actually make a single Onscreen MSAA and Onscreen Depth/Stencil and share them across the swapchain images - as they should be effectively synchronized already.
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
jonahwilliams commentedon Mar 5, 2024
The primary trick here is making sure that the transient attachments for the onscreen (MSAA and Depth/Stencil) are effectively recycled. In fact, I think we can actually make a single Onscreen MSAA and Onscreen Depth/Stencil and share them across the swapchain images - as they should be effectively synchronized already.
[Impeller] fold memory check into allocator_vk (#51187)
[Impeller] measure GPU memory usage. (#144575)
Reverts "[Impeller] fold memory check into allocator_vk (#51187)" (#5…
[Impeller] add a per-frame trace event for heap usage on Vulkan. (#51246
[Impeller] More efficient usage of transient onscreen attachments. (#…
jonahwilliams commentedon Mar 8, 2024
At least on average frame time, this is now faster than it was with GLES. Waiting for more data points for 90%+
jonahwilliams commentedon Mar 11, 2024
This is done!
github-actions commentedon Mar 25, 2024
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.