[GLUTEN-9196][CH] Use wide-table aggregation to eliminate multi-table joins#9155
[GLUTEN-9196][CH] Use wide-table aggregation to eliminate multi-table joins#9155lgbo-ustc merged 10 commits intoapache:mainfrom
Conversation
|
Run Gluten Clickhouse CI on x86 |
|
Run Gluten Clickhouse CI on x86 |
|
Run Gluten Clickhouse CI on x86 |
1 similar comment
|
Run Gluten Clickhouse CI on x86 |
|
Run Gluten Clickhouse CI on x86 |
1 similar comment
|
Run Gluten Clickhouse CI on x86 |
|
Run Gluten Clickhouse CI on x86 |
|
Run Gluten Clickhouse CI on x86 |
|
Run Gluten Clickhouse CI on x86 |
lgbo-ustc
changed the title
|
Run Gluten Clickhouse CI on x86 |
|
Run Gluten Clickhouse CI on x86 |
|
Run Gluten Clickhouse CI on x86 |
|
Run Gluten Clickhouse CI on x86 |
|
When querying only two tables, the optimization does not significantly improve execution speed. However, when querying three tables, the optimized query speed shows a noticeable improvement. This is partly because as the number of tables involved in the query increases, the join method requires building more hash tables. Additionally, the more join operations performed within a single node, the more likely it is to trigger memory spill operations, which further slows down execution. |
|
Run Gluten Clickhouse CI on x86 |
|
Run Gluten Clickhouse CI on x86 |
|
Run Gluten Clickhouse CI on x86 |
lgbo-ustc
changed the title
|
Run Gluten Clickhouse CI on x86 |
2 similar comments
|
Run Gluten Clickhouse CI on x86 |
|
Run Gluten Clickhouse CI on x86 |
|
Run Gluten Clickhouse CI on x86 |
2 participants
What changes were proposed in this pull request?
(Please fill in changes proposed in this fix)
Fixes: #9196
How was this patch tested?
(Please explain how this patch was tested. E.g. unit tests, integration tests, manual tests)
(If this patch involves UI changes, please attach a screenshot; otherwise, remove this)