-
Notifications
You must be signed in to change notification settings - Fork 915
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
Update default data source in cuio reader benchmarks #12740
Update default data source in cuio reader benchmarks #12740
Conversation
@@ -72,7 +72,7 @@ void BM_orc_read_data(nvbench::state& state, nvbench::type_list<nvbench::enum_ty | |||
data_profile_builder().cardinality(cardinality).avg_run_length(run_length)); | |||
auto const view = tbl->view(); | |||
|
|||
cuio_source_sink_pair source_sink(io_type::HOST_BUFFER); | |||
cuio_source_sink_pair source_sink(io_type::FILEPATH); |
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.
ooh, I didn't fully comprehend the proposed change until now.
I would argue that HOST_BUFFER is a better choice here (device buffer is the best option IMO) because this set of benchmarks is meant to benchmark only the decode part of the reader (the name is "orc_read_decode"). I understand that this leaves us with a gap in benchmark coverage (different types + IO). maybe that should either be a separate benchmark or an option.
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.
But the issue#12678 says:
|
/merge |
Closes #12678
This PR sets the default data source in orc, parquet and csv reader benchmarks to
DEVICE_BUFFER
.Description
Checklist