-
Notifications
You must be signed in to change notification settings - Fork 930
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
[DRAFT] [DEMO] [SPARK] Use explicit Rowset time formatters for improving RowSet generation #5815
[DRAFT] [DEMO] [SPARK] Use explicit Rowset time formatters for improving RowSet generation #5815
Conversation
I don't see any changes related to primitive data types, can you increase the number of rows and try a few more times? |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #5815 +/- ##
============================================
+ Coverage 61.36% 61.41% +0.04%
Complexity 23 23
============================================
Files 608 608
Lines 35941 35944 +3
Branches 4940 4940
============================================
+ Hits 22056 22075 +19
+ Misses 11494 11482 -12
+ Partials 2391 2387 -4 ☔ View full report in Codecov by Sentry. |
@bowenliang123 I guess the overhead may come from the always construction of |
Yes. For most cases, shown from evidence. But the overhead for primitive types should not comes from the data types, the time formatters are reused in the whole stage of TRowSet generation. Still have to see more evidence for repeated tests. Please consider merge #5809 to introduce benchmark with warmups and repeating rounds, for the reference of further investigation. |
I think this is an obvious improvement. The benchmark unit test is controversial and not required, we can remove it first and continue reviewing the PR. |
Closing this PR with no enough consensus on the purposes, the design, the changes and the approaches. |
🔍 Description
Issue References 🔗
Subtask of #5808.
Describe Your Solution 🔧
Types of changes 🔖
Test Plan 🧪
Behavior Without This Pull Request ⚰️
Behavior With This Pull Request 🎉
Related Unit Tests
Checklists
📝 Author Self Checklist
📝 Committer Pre-Merge Checklist
Be nice. Be informative.