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

Posted to issues@spark.apache.org by "Liang-Chi Hsieh (JIRA)" <ji...@apache.org> on 2017/08/13 06:05:00 UTC

[jira] [Created] (SPARK-21717) Decouple the generated codes of consuming rows in operators under whole-stage codegen

Liang-Chi Hsieh created SPARK-21717:
---------------------------------------

             Summary: 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


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
(v6.4.14#64029)

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