Data optimizer #4
Merged
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
dudewad
force-pushed
the
data-optimizer
branch
from
c549fb4 to
85ba1f3
Compare
…derer. Reduces render time by almost 50%.
dudewad
force-pushed
the
data-optimizer
branch
from
85ba1f3 to
6997f3c
Compare
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.
By converting the star catalog data to an optimized format we can pre-compute a lot of star data. This reduces runtime calculation significantly, dropping render times from 10+ seconds down to ~5-6 seconds.
Not fast enough, but a marked improvement thus far.
The good thing about the optimizer is that it allows the renderer to be flexible - as long as star data comes in a csv with the right formats (see readme) any catalog can be used.