You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Xiao Li (JIRA)" <ji...@apache.org> on 2017/10/04 17:10:01 UTC

[jira] [Resolved] (SPARK-21871) Check actual bytecode size when compiling generated code

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

Xiao Li resolved SPARK-21871.
-----------------------------
       Resolution: Fixed
    Fix Version/s: 2.3.0

> Check actual bytecode size when compiling generated code
> --------------------------------------------------------
>
>                 Key: SPARK-21871
>                 URL: https://issues.apache.org/jira/browse/SPARK-21871
>             Project: Spark
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions: 2.2.0
>            Reporter: Takeshi Yamamuro
>            Assignee: Takeshi Yamamuro
>            Priority: Minor
>             Fix For: 2.3.0
>
>
> In SPARK-21603, we added code to give up code compilation and use interpreter execution in SparkPlan if the line number of generated functions goes over maxLinesPerFunction. But, we already have code to collect metrics for compiled bytecode size in `CodeGenerator` object. So, I think we could easily reuse the code for this purpose.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org