Add Basic Pipeline Cache to Bitonic Sort #416
Open
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
…impetus behind pipeline caching in comments, and directed viewer to relevant toji article within said comment
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.
Added a basic pipeline cache to the bitonic sort sample, as well as comments attempting to explain the impetus behind using a pipeline cache.
Although the bitonic sort example doesn't particularly benefit from a pipeline cache in the same way a GLTF renderer might, I believe its still beneficial to surface this pattern in simpler contexts as a way of clearly conveying how such a pattern might be used (i.e in scenarios where multiple pipelines are being created based on arguments from incoming data or user input, and those arguments may be repeated across multiple calls to those pipelines).