Document Metal Gaussian GPU execution strategy - #108
Merged
Merged
Conversation
4 tasks done
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
Record the proposed Metal Gaussian GPU execution strategy in a standalone design document, with links from the shared Gaussian design and backlog. The plan sequences measurement and shared Slang shaders, persistent attributes and GPU execution through raster, then tile rasterization and Apple GPU tuning.
It defines acceptance gates, CPU reference/fallback behavior, image and performance evidence, and deferred optimizations. Implementation support remains documented separately from proposed work.
Related PR: #107.
Impact
Verification
git diff --checkpasses.Review checklist