Native Arrays #51
Open
Native Arrays #51
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
added 4 commits
March 25, 2017 21:04
I was re-rendering the _entire_ scene for _every_ sprite _every_ frame. I'm amazed it was running as well as it did!
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.
First attempt at performance improvement. Still need to benchmark this, but I've replaced all Arrays with Native (Fiddle malloc'd) arrays where possible.
In some cases, native arrays actually make things slower. I need to find out where these places are and try and find the best compromise.
E.g, I tried to use native arrays for Matrix elements, but that slowed things down because they're modified and read in Ruby-land a lot, and with pack/unpack that's a lot of unnecessary string/array allocations.
I haven't really noticed anything running faster yet. I might need to see where the real performance hits are happening. Theoretically, passing big data arrays (think, all those vertices) from Ruby to C will be more efficient now (I think? I hope!).