[ https://issues.apache.org/jira/browse/SPARK-21717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wenchen Fan resolved SPARK-21717. --------------------------------- Resolution: Fixed Fix Version/s: 2.3.0 Issue resolved by pull request 18931 [https://github.com/apache/spark/pull/18931] > Decouple the generated codes of consuming rows in operators under whole-stage > codegen > ------------------------------------------------------------------------------------- > > Key: SPARK-21717 > URL: https://issues.apache.org/jira/browse/SPARK-21717 > Project: Spark > Issue Type: Improvement > Components: SQL > Affects Versions: 2.2.0 > Reporter: Liang-Chi Hsieh > Assignee: Liang-Chi Hsieh > Priority: Critical > Fix For: 2.3.0 > > > It has been observed in SPARK-21603 that whole-stage codegen suffers > performance degradtion, if generated functions are too long to be optimized > by JIT. > We basically produce a single function to incorporate generated codes from > all physical operators in whole-stage. Thus, it is possibly to grow the size > of generated function over a threshold that we can't have JIT optimization > for it anymore. > This ticket is trying to decouple the logic of consuming rows in physical > operators to avoid a giant function processing rows. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org