rendering: reuse retained plan and resource work - #77
Merged
tritao merged 0 commit intoAug 23, 2026
Merged
Conversation
tritao
force-pushed
the
integration/retained-performance-wip
branch
from
August 22, 2026 22:05
71cc058 to
d80c8b2
Compare
tritao
force-pushed
the
stack/retained-workload-coverage
branch
from
August 23, 2026 01:44
58d328f to
921ebce
Compare
tritao
force-pushed
the
integration/retained-performance-wip
branch
from
August 23, 2026 01:44
d80c8b2 to
9f6c844
Compare
Collaborator
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Performance
At 50k shared-recipe occurrences, transform/material update frames improve from roughly 41-46 ms to 16-18 ms on the tested Intel/Mesa hardware. Plan construction drops to zero and GPU-resource validation falls below 0.001 ms for eligible updates.
Validation