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

NUMA-awareness for separate join build

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Backend
    • Labels:

      Description

      Currently joins are executed by a single thread, so generally the memory allocations will come from the local NUMA node (assuming the thread stays on the same NUMA node).

      With the separate join build on a NUMA machine, some probe threads will likely be on a different NUMA node from the build, resulting in inefficiency. This may not be a major problem because of prefetching, etc, but filing this JIRA to track the potential issue.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              tarmstrong Tim Armstrong
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: