-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Fix SortExec bench case and Add SortExec input cases to bench for SortPreservingMergeExec #5308
Conversation
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.
Thank you @jaylmiller
let plan = Arc::new(SortExec::try_new(sort, Arc::new(exec), None).unwrap()); | ||
let exec = Arc::new(CoalescePartitionsExec::new(Arc::new(exec))); | ||
let plan = Arc::new(SortExec::try_new(sort, exec, None).unwrap()); |
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.
without this change it was only ever benchmarking the case where the execute
receives a single record batch to sort.
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.
LGTM -- thank you @jaylmiller
Benchmark runs are scheduled for baseline = 222205d and contender = e13c653. e13c653 is a master commit associated with this PR. Results will be available as each benchmark for each run completes. |
…tPreservingMergeExec (apache#5308) * add SortExec input case to each merge bench case * fix lil typo error in sort bench * fix sort bench to actually use full data set in non-preserve partition case
Which issue does this PR close?
#5230 (does not close it.)
Rationale for this change
The current SortPreservingMergeExec benchmarks take MemoryExec as input. In #5230 we want to modify SortPreservingMergeExec and SortExec so that when row encoding is used within the sort node, it is preserved for usage by the merge node.
Which means, we need bench cases on main for SortPreservingMergeExec when it has SortExec as input to see if the changes for #5230 are helping perf.
Additionally, the logic in the SortExec bench for the case where
preserve_partitioning=false
was flawed, so that has been fixed too.What changes are included in this PR?
Are these changes tested?
n/a
Are there any user-facing changes?
no