-
Notifications
You must be signed in to change notification settings - Fork 29k
[SPARK-25931][SQL] Benchmarking creation of Jackson parser #22920
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
Closed
Closed
Changes from 2 commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
f31e438
Re-run the benchmark before changes
MaxGekk c7d5cc4
Invoke Jackson parser in benchmarks
MaxGekk 07780dc
Merge remote-tracking branch 'origin/master' into json-benchmark-foll…
MaxGekk 0e99831
Removing filter from count benchmarks
MaxGekk 02d01f3
Renaming existing benchmarks
MaxGekk eeb7c69
Added new benchmark
MaxGekk 9e32447
Updating benchmark results
MaxGekk d46e945
Update iteration and result.
dongjoon-hyun 4ecc7e0
Merge pull request #14 from dongjoon-hyun/PR-22920
MaxGekk File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
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.
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.
@MaxGekk . This is another benchmark case, isn't it?
We should have different benchmark cases for these.
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 is not a follow-up. Please create another JIRA to add these test cases.
Uh oh!
There was an error while loading. Please reload this page.
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.
Originally I added the benchmark to check how specifying of
encodingimpacts on performance (see #20937). This worked well till #21909 . Currently the benchmark just test how fast JSON datasource can create empty rows (in the case ofcount()) which is checked by another benchmark.I believe this PR is just follow up of #21909 which must include the changes proposed in the PR.
Uh oh!
There was an error while loading. Please reload this page.
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.
@MaxGekk . In your PR (#21909), you already showed the effect via benchmark .
What I mean is both test cases are meaningful and worth to have. :) And, we need to compare both results in the future release.
In any way, please create new different benchmark cases for this PR.
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.
BTW, how do you want to call old and new test cases?
JSON per-line parsing:looks not a little bit accurate because we have filters now.