[
https://issues.apache.org/jira/browse/SPARK-44485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hyukjin Kwon resolved SPARK-44485.
----------------------------------
Fix Version/s: 3.5.0
4.0.0
Resolution: Fixed
Issue resolved by pull request 42095
[https://github.com/apache/spark/pull/42095]
> optimize generateTreeString code path
> -------------------------------------
>
> Key: SPARK-44485
> URL: https://issues.apache.org/jira/browse/SPARK-44485
> Project: Spark
> Issue Type: Improvement
> Components: Spark Core
> Affects Versions: 3.4.1
> Reporter: Ziqi Liu
> Assignee: Ziqi Liu
> Priority: Major
> Fix For: 3.5.0, 4.0.0
>
>
> In `TreeNode.generateTreeString`, we observed inefficiency in scala
> collection operations and virtual function call.
> This inefficiency become significant in large plan (we hit a example of more
> than 1000 nodes). So {*}it’s worth optimizing the super hot code path{*}. By
> rewriting into native Java code(not so sweet as scala syntax sugar though),
> we should be able to get rid of most of the overhead.
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
