Performance Enhancement: Font rendering in a single drawcall#2791
Open
Vwing wants to merge 1 commit into
Open
Conversation
Author
|
Note the drawcalls could be reduced further in books by batching lines together, and I believe I'm doing that in the Android fork, but it might cause some appearance differences. Will examine later, but it's a lower priority; I think this PR is fine without that addition. |
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.
Both SDF and classic fonts were being rendered a single character at a time, causing potentially tens of thousands of draw calls in a single frame. I've reduced it down to a single draw call per text item.
Before (18k draw calls and 30 fps):

After (500 draw calls and 60 fps):

The old multi-call path is still present and called if and when an error ever occurs in the new path.