Compute Cache API and Hash API #98
Draft
Conversation
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
1 participant
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.
This is preliminary work for the comptue cache API, which i'm convinced is almost vestigial in terms of it's performance gains. There was a real lack of examples of effects which do long running simulations. The adobe particle effects are all deterministic afaict. There is a closed source rust plugin called stipple which uses the compute cache to great advantage and I wanted to see how far the benefits of intermittent caching could get us.
out2.webm
For this to work we would need to update the bindgen and release it.
Todo:
[ ] - update windows bindgen
[ ] - test on windows