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
Use nvcomp's snappy compressor in ORC writer #9242
Use nvcomp's snappy compressor in ORC writer #9242
Changes from 30 commits
db23741
a5f3363
61018aa
64d7d1c
27764e7
95a57ec
cc9500a
7989b9c
f90409c
40ebd1e
4a2cb24
6019b0f
140d3d0
05f5343
62d92b4
3c73be3
e0a013d
7501b11
bfa1366
203cf15
99e4f80
6721fb8
5391e13
354e229
66d49e8
4e78529
8ed68ef
8b471de
34a42c3
0569281
11e20e7
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Isn't it mildly worse to pass a span here if you don't ever use the size? In the sense of having to hypothetically push another argument on the stack.
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.
As I see it, the trade-off is that with span it's clear that the parameter is an array, not a pointer to a single object. Now, whether this is a good trade-off is up for debate :D
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.
Could this be replaced with a
thrust::transform_output_iterator
in the call tonvcompBatchedSnappyCompressAsync
, basically to safe allocating and materializing thecompressed_bytes_written
? [1][1] https://thrust.github.io/doc/classthrust_1_1transform__output__iterator.html
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.
nvcompBatchedSnappyCompressAsync
is a C API and doesn't take iterators. 😞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.
Oh, I see. Too bad! Thanks for clarifying 👍