Uh oh!
There was an error while loading. Please reload this page.
Revert "[SPARK-21052][SQL] Add hash map metrics to join" - #23204
Conversation
JkSelf
commented
Dec 3, 2018
Cluster info:
Related parameters setting:
In above test environment, we found a serious performance degradation issue in Spark2.3 when running TPC-DS on SKX 8180. We investigated this problem and figured out the root cause is in community patch SPARK-21052 which add metrics to hash join process. And the impact code is L486 and L487 . Following is the result of TPC-DS Q19 in spark2.1, spark2.3 remove L486&487, spark2.3 add L486&487 and spark2.4.
|
cloud-fan
commented
Dec 3, 2018
ok to test |
There was a problem hiding this comment.
I know it's easy to just run the git revert command, but I'd like to manually revert it, since that PR was merged long time ago. And we should still keep changes like this renaming, as they are not quite related to the performance regression.
There was a problem hiding this comment.
ditto, it's better to put this code block here, let's keep this change.
cloud-fan
commented
Dec 3, 2018
I'm fine to revert it if it caused a significant performance regression, we should revisit it later, with different ideas, like updating the metrics for each batch instead of each record. |
There was a problem hiding this comment.
I think we can keep the changes in this file as well.
There was a problem hiding this comment.
If as your test shows this is the cause of performance regression, we can just revert this and related changes. The change in HashAggregateExec, etc. can be kept.
There was a problem hiding this comment.
+1, like I said in https://github.com/apache/spark/pull/23204/files#r238257371
viirya
commented
Dec 3, 2018
Is this observable in general hash join query, except for TPC-DS Q19? |
SparkQA
commented
Dec 3, 2018
Test build #99615 has finished for PR 23204 at commit
|
LuciferYang
commented
Dec 4, 2018
@cloud-fan@viirya#23214 maybe reslove this problem and we needn't revert this patch. |
dongjoon-hyun
commented
Dec 9, 2018
Hi, @LuciferYang . If we are not going to revert this, could you close this PR? |
cloud-fan
commented
Dec 9, 2018
according to #23214 (comment) , the hash join metrics is wrongly implemented. I think it's fine to revert it and re-implement it later. @JkSelf can you address the comments and only revert the hash join part? thanks! |
JkSelf
commented
Dec 9, 2018
The result of all queries in tpcds with 1TB data scale is in tpcds result |
JkSelf
commented
Dec 9, 2018
@cloud-fan ok, i will revert as your comments later. |
dongjoon-hyun
commented
Dec 9, 2018
@cloud-fan and @JkSelf . |
cloud-fan
commented
Dec 9, 2018
+1 |
LuciferYang
commented
Dec 10, 2018
@cloud-fan If we decide to partial revert SPARK-21052 and no need for #23214, I will close it. |
cloud-fan
commented
Dec 10, 2018
If we can quickly finish #23214 (within several days), let's go for it. But if we can't, I'd suggest we do the partial revert first to fix the perf regression, and add back the metrics later. |
JkSelf
commented
Dec 10, 2018
@cloud-fan@dongjoon-hyun update the patch, please help review if you have time. Thanks. |
LuciferYang
commented
Dec 10, 2018
ok~ already close #23214 |
cloud-fan
commented
Dec 10, 2018
can we follow #23204 (comment) and create a new ticket? |
SparkQA
commented
Dec 10, 2018
Test build #99894 has finished for PR 23204 at commit
|
JkSelf
commented
Dec 10, 2018
@cloud-fan the new ticket is in here. I will close this ticket. |
| } | ||
| // At the end of the task, we update the avg hash probe. | ||
| TaskContext.get().addTaskCompletionListener[Unit](_ => |
There was a problem hiding this comment.
in this file, the join method takes avgHashProbe: SQLMetric, we should remove it.
There was a problem hiding this comment.
@cloud-fan updated in new PR #23269 Thanks.
dongjoon-hyun
commented
Dec 10, 2018
I'll close this in order to collect the reviews into new PR, #23269 . |
Partial revert SPARK-26155, because of the performance degradation in TPC-DS result with 1TB data scale.