Skip to content
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

Reduce optimizer.max-reordered-joins default to 8 #21360

Merged
merged 1 commit into from
Apr 3, 2024

Conversation

raunaqmorarka
Copy link
Member

@raunaqmorarka raunaqmorarka commented Apr 2, 2024

Description

Reduces planning time for tpcds/q64 from 11.8s to 6.6s at sf1k by reducing the default of optimizer.max-reordered-joins to 8 from 9. q64 is the only TPC query affected, it has a different join order but it’s execution was not slowed compared to before.
Further reduction to 7 helps some more with planning time but the plan for q72 becomes worse, so we leave it at 8.

Additional context and related issues

Release notes

( ) This is not user-visible or is docs only, and no release notes are required.
( ) Release notes are required. Please propose a release note for me.
(x) Release notes are required, with the following suggested text:

# General
* Improve planning time for queries with large number of joins. ({issue}`21360`)

Reduces planning time for tpcds/q64 from 11.8s to 6.6s
@cla-bot cla-bot bot added the cla-signed label Apr 2, 2024
@raunaqmorarka raunaqmorarka requested review from martint and sopel39 April 2, 2024 15:27
@github-actions github-actions bot added the docs label Apr 2, 2024
@raunaqmorarka
Copy link
Member Author

Hive partitioned parquet sf1k tpcds/q64
291407492-0ae179b8-2a17-4252-8b78-dddd9203f5bb

Hive unpartitioned parquet sf1k tpcds/q64
291408970-8032cf66-3211-4d4f-aa7a-4f8cb8689f79

@raunaqmorarka raunaqmorarka merged commit 6b0b2e8 into trinodb:master Apr 3, 2024
98 checks passed
@raunaqmorarka raunaqmorarka deleted the max-reordered branch April 3, 2024 10:18
@github-actions github-actions bot added this to the 444 milestone Apr 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

2 participants