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

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

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 1.8.0
    • perf, tserver
    • None

    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

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

            Dates

              Created:
              Updated:
              Resolved: