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

Remove redundant remote exchanges due to missing unaliasing #2853

Merged
merged 2 commits into from
Feb 21, 2020

Conversation

sopel39
Copy link
Member

@sopel39 sopel39 commented Feb 17, 2020

No description provided.

@sopel39
Copy link
Member Author

sopel39 commented Feb 17, 2020

Removes redundant remote exchange from TPCH/q04

@sopel39
Copy link
Member Author

sopel39 commented Feb 17, 2020

This also makes planning more deterministic as unaliasing after reorder joins behaved differently depending if there were more predicates (derived from table scan handle) that could be inferred.

@sopel39
Copy link
Member Author

sopel39 commented Feb 18, 2020

Benchmarks. One can see some overhead of join using dictionaries (q23_1, q23_2)

Benchmarks comparison-unalias.pdf

@sopel39
Copy link
Member Author

sopel39 commented Feb 18, 2020

#2862 fixes most of the observed CPU perf penalty.

Benchmarks comparison-fix.pdf

Symbols used in equi conditions have same types always.
@sopel39 sopel39 merged commit 4a52b0b into trinodb:master Feb 21, 2020
@sopel39 sopel39 deleted the ks/unalias_fix branch February 21, 2020 10:48
@sopel39 sopel39 mentioned this pull request Feb 21, 2020
6 tasks
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.

3 participants