You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Remove unnecessary null checks in GroupColumns #12944
The challenge is that, we should refactor codes to support vectorize append firstly.
(otherwise, we need to add a branch about which append function we should call for each row's appending, and as a reuslt, we remove a row level branch and add another...)
Makes sense to vectorize appends at the same time, I think this might have even more impact than just omitting null checks.
Removing the null check, but adding another branch will likely not yield any benefit.
Makes sense to vectorize appends at the same time, I think this might have even more impact than just omitting null checks. Removing the null check, but adding another branch will likely not yield any benefit.
I wonder should we vectorize eq together.
I impl a simple version only vectorize the append operation #12996
The benchmark number is generated from it.
But it introduce another branch in the equal_to stage, which I think maybe switching to the all vectorize approach like duckdb can eliminate this new branch.
Activity
Rachelint commentedon Oct 15, 2024
I am working on a poc #12947 for checking the improvement of this idea.
Rachelint commentedon Oct 16, 2024
I found it actually now a trivial change.
The challenge is that, we should refactor codes to support vectorize append firstly.
(otherwise, we need to add a branch about which append function we should call for each row's appending, and as a reuslt, we remove a row level branch and add another...)
I am trying it.
Rachelint commentedon Oct 17, 2024
This is the number get from my local:
Dandandan commentedon Oct 17, 2024
Makes sense to vectorize appends at the same time, I think this might have even more impact than just omitting null checks.
Removing the null check, but adding another branch will likely not yield any benefit.
Rachelint commentedon Oct 18, 2024
I wonder should we vectorize eq together.
I impl a simple version only vectorize the append operation #12996
The benchmark number is generated from it.
But it introduce another branch in the
equal_tostage, which I think maybe switching to the all vectorize approach likeduckdbcan eliminate this new branch.Rachelint commentedon Dec 1, 2024
finished in #12996