You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Hyukjin Kwon (Jira)" <ji...@apache.org> on 2023/07/22 07:44:00 UTC

[jira] [Assigned] (SPARK-44485) optimize generateTreeString code path

     [ https://issues.apache.org/jira/browse/SPARK-44485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hyukjin Kwon reassigned SPARK-44485:
------------------------------------

    Assignee: Ziqi Liu

> 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
>
> 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: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org