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
Introduce benchmark suite for JSON reader options #15124
Introduce benchmark suite for JSON reader options #15124
Changes from 16 commits
b2a7c45
bc42243
f2dd994
2ae3633
ea4d9b7
56317bd
a1bc431
5c0de81
72b070d
e04db8b
b470334
dc799c2
f926172
6c75aee
14435e0
5f331e2
6c3604b
5661a4a
12cfaba
300753c
3a79368
66552a5
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.
Oh no this is too many template params. Why not using run time parameter instead? That would reduce compile time a lot.
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 followed the design for benchmarking reader options in orc and parquet. Would we have to modify those benchmarks as well to maintain similar design?
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.
This makes results more readable and the build time for benchmarks doesn't really matter IMO.
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.
Yeah that's fine to me 👍
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.
While we are testing the options, I would recommend making
lines
into an nvbench enum axis as well. Although since some of the options require lines to be true, maybe benchmarking lines true/false should be a separate benchmark.nvbench::enum_type_list<row_selection::ALL, row_selection::BYTE_RANGE>,
lines=Truenvbench::enum_type_list<normalize_single_quotes::NO, normalize_single_quotes::YES>
line=True/Falsenvbench::enum_type_list<mixed_types_as_string::NO, mixed_types_as_string::YES>
line=True/Falsenvbench::enum_type_list<recovery_mode::RECOVER_WITH_NULL, recovery_mode::FAIL>))
lines=TrueAfter thinking through the options, I don't think we need to test
normalize_single_quotes
andmixed_types_as_string
withlines=false
. It still might be useful to add a lines true/false benchmark without any additional options. If others agree then that could be a follow-on PR.