Uploaded image for project: 'IMPALA'
  1. IMPALA
  2. IMPALA-5443

Consider automatically disabling codegen per ExecNode based on planner estimates

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Open
    • Minor
    • Resolution: Unresolved
    • Impala 2.9.0
    • None
    • Frontend

    Description

      We should consider automatically disabling codegen per plan node based on the number of input/output rows. We have the plumbing already in place (it's used to disable codegen for non-grouping merge aggregations) but choosing and implementing a good policy is trickier.

      We should be conservative about doing this, because the cost of codegen is O(1) but the runtime speedup is O(n).

      Attachments

        Issue Links

          is related to

          Improvement - An improvement or enhancement to an existing feature or task. IMPALA-2651 codegen overhead can be high

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          Improvement - An improvement or enhancement to an existing feature or task. IMPALA-5483 Consider automatically disabling codegen for entire query based on planner estimates

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          Activity

            People

              MikaelSmith Michael Smith
              tarmstrong Tim Armstrong
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated: