Draft
Conversation
added 3 commits
January 23, 2026 19:43
Member
Author
|
4.3ms -> 3.6ms on tiger |
added 2 commits
January 24, 2026 20:37
Member
Author
|
~3.6ms -> ~2.8ms on tiger. Things that I tried but were either the same perf or worse:
Last thing that could be tried is switching from processing by row to processing by column. This would at the very least save the transpose necessary before writing to the alpha buffer. |
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.
Uploading this as a potential feature, and if we do want to land it, I can polish it up from here. Currently, the performance is pretty bad, about 3x Analytic anti-aliasing (~4.3ms vs ~1.5ms on tiger). However, the pixel intersection logic is currently written GPU-ish style, and I can imagine switching to more serial friendly DDA approach could yield some savings.