add text_perf example #348
Merged
+95
−1
Conversation
This file contains 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
the docs have been refined just a little bit, but this adds an example on how to render a lot of text and be able to benchmark the performance
17cupsofcoffee
approved these changes
Aug 5, 2024
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.
the docs have been refined just a little bit, but this adds an example
on how to render a lot of text and be able to benchmark the performance
based on this info! #347 (comment)
Much like bunnymark, the new example makes it easy to render a lot of
text by pressing the SPACE bar. In release builds, I'm seeing 12k instances
stay at steady 60 FPS on my MacBook! Beyond that it starts to drop frames.