Improve performance of projection #1028
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
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.
Following #1023 this PR adds hashed column retrieval when there are more than 300 columns.
The naive algorithm for finding named columns was a linear search through all column names. Because there are also several layers of indirection this can become slow. Especially in the issue discussed where there were more than 2M columns.
For the lazy projection an optimization rule was added. In case of simple projection, being
Vec<col(..)>we don't throw the projection on the threadpool, but we simply call the eagerDataFrame,select.@ghuls, can you take this for a spin? :)