Repository navigation
Avoid reduction overhead in hash join probe kernels - #24706
PointKernel wants to merge 2 commits into
Conversation
Select separate sum and no-sum kernel specializations on the host so match contexts and join retrieval do not reserve reduction resources. Retain the fused reduction for size queries and shared probing logic.
|
Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually. Contributors can view more details about this message here. |
|
/ok to test |
|
Before/after performance for match-count contexts and partitioned joins, using
python python/scripts/nvbench_compare.py --no-color baseline.json candidate.json[0] NVIDIA RTX PRO 6000 Blackwell Workstation Edition
inner_join[0] NVIDIA RTX PRO 6000 Blackwell Workstation Edition
|
Description
Follow-up to #24637. Match contexts and join retrieval pass a null
total_matchespointer, but the runtime guard still gives their probe kernel the register and shared-memory footprint of the fused size reduction.Select separate sum and no-sum kernel specializations in the host launcher. Match contexts, ordinary retrieval, and partitioned retrieval use a kernel without the sum accumulator or block reduction, while size queries retain the fused reduction and its memory savings. Both specializations keep the same probing and full-join bookkeeping logic.
Checklist