[ios] Using SIMD to replace vector_float types can boost CPU performance on mid-range models. #2720
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
…nce on mid-range models.
|
This is excellent, thank you! I'm actually surprised, that the compiler doesn't auto-vectorize most of this, and that changes to the shader have an impact on CPU usage. |
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.
I've been working on further optimizing Spine performance lately. For Spine files with a lot of vertices on mid-range devices with moderate performance, using SIMD significantly optimizes CPU usage, reducing it by about 10 to 20%. However, for files with a typical vertex count on high-end flagship devices, the optimization gains from SIMD aren't as pronounced, only reducing CPU usage by about 4%.