CUDA: promote opt-in exact bitmap join plans - #92
Merged
Merged
Conversation
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Scope
Promote the reusable opt-in exact bitmap join implementation, not the DOOP research archive or generated query variants.
with_plan(dedup_bitmap=True)through DSL, HIR/MIR, index planning, and full CUDA runner emission.examples/doop.pyand default planning unchanged. No automatic optimizer selection or end-to-end speedup claim.Verification
Full twelve-dataset GPU timing/correctness is not claimed: an existing vLLM process occupies most of the 48 GB GPU. The next stacked PR supplies CPU/GPU execution and exact cross-backend comparison.
Stack
Depends on #91 for review ordering; merge after that PR. This commit contains only compiler/runtime bitmap support and its documentation/tests.