Uploaded image for project: 'Kudu'
  1. Kudu
  2. KUDU-2380

Selective predicates when selecting high number of columns burns CPU in SerializeRowBlock

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.8.0
    • Component/s: perf, tserver
    • Labels:
      None
    • Target Version/s:

      Description

      Testing a table with 280 columns, I found the following performance characteristic:

      • scanning all 280 columns with a selective non-key predicate which matches 0 rows took 8.28s
      • scanning no columns (count query) with the same predicate which matches 0 rows took 314ms.

      This suggests that we are burning 96% of our CPU doing useless work for this query.

        Attachments

          Activity

            People

            • Assignee:
              tlipcon Todd Lipcon
              Reporter:
              tlipcon Todd Lipcon
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: