We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
There are several issues labeled with joins and performance. This is a meta issue to give a high level view on the topics, problems and opportunities.
joins
performance
Bad table swap/join ordering: Poor query performance with numerous (outer) joins #13855
Consider table stats/cardinality when choosing hash join. A case where hash join leads to bad results: Hash join where right side is empty/has no match: Build phase of left side is run and expensive, see INNER JOIN on empty selection takes really long and/or fails with CurcuitBreaker #11050.
Transitive closure join optimization: Transitive Closure JOIN Optimization #10208
max/min values from table functions: Optimise join performance involving generate_series #11417
Allow hints around the type and order of JOIN operations #13283
Optimizer rule for pushing down correlated joins beneath outer multi joins #13671
Sorted merge join (https://en.wikipedia.org/wiki/Sort-merge_join)
Group join
Lookup join (Client side joins are significantly faster in some cases #11183)
Vectorized join execution
Hashing strategies, bloom filters, disk-spill-over, temp tables
Range join optimizations (https://duckdb.org/2022/05/27/iejoin.html)
NestedLoopJoin
GenericFunctionQuery
The text was updated successfully, but these errors were encountered:
No branches or pull requests
There are several issues labeled with
joins
andperformance
.This is a meta issue to give a high level view on the topics, problems and opportunities.
Optimizer improvements
General
Concrete examples
Bad table swap/join ordering: Poor query performance with numerous (outer) joins #13855
Consider table stats/cardinality when choosing hash join. A case where hash join leads to bad results: Hash join where right side is empty/has no match: Build phase of left side is run and expensive, see INNER JOIN on empty selection takes really long and/or fails with CurcuitBreaker #11050.
Transitive closure join optimization: Transitive Closure JOIN Optimization #10208
max/min values from table functions: Optimise join performance involving generate_series #11417
Allow hints around the type and order of JOIN operations #13283
Optimizer rule for pushing down correlated joins beneath outer multi joins #13671
Execution strategies/engine
Sorted merge join (https://en.wikipedia.org/wiki/Sort-merge_join)
Group join
Lookup join (Client side joins are significantly faster in some cases #11183)
Vectorized join execution
Compiled and Vectorized Queries But Were Afraid to Ask
Hashing strategies, bloom filters, disk-spill-over, temp tables
Range join optimizations (https://duckdb.org/2022/05/27/iejoin.html)
Unclassified
NestedLoopJoin
withGenericFunctionQuery
#13184Correlated sub-queries
The text was updated successfully, but these errors were encountered: