perft: lazy render model after event loop #1532
Closed
+48
−13
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.
On a large program, this can reduce repeated model render calls when the model is getting updated rapidly. This change makes the model stored as an atomic pointer for safe concurrent access between the event loop and the render loop.
The model is now stored internally as an atomic pointer, and updated after each event loop iteration. The render loop reads the latest model from the atomic pointer before rendering its View.
Benchmarks show a slight reduction in allocations for the TeaTest example.