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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Large strings support in cudf::merge #15374
Large strings support in cudf::merge #15374
Changes from 22 commits
f71aabd
31ed7c2
09c98a5
32199eb
2aa149f
998208d
de4f0a2
a8d51e2
6f43aba
890d8d1
a2faab1
8ee448a
0d648b4
540ee80
b16a099
5554e03
1a78415
23509b3
1f4c22f
34dd22f
b2f5c3e
ace98cd
8eafd8f
45853b9
c194c1b
5684ba9
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
This file was deleted.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Once large strings are the default behavior, I wonder if we should do a first pass in int64 and then cast the offsets down if it fits in int32, rather than recomputing as int64 on overflow. I don't know how expensive the downcast would be compared to recomputing. Of course this also depends on whether we expect large strings to be common. I don't expect any action here, but would be open to your thoughts.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't really expect large strings to be very common. At least not in the near to mid future.
I'd rather force any performance hit into the int64 path right now if possible.