[
https://issues.apache.org/jira/browse/IMPALA-9186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Armstrong updated IMPALA-9186:
----------------------------------
Parent: (was: IMPALA-3902)
Issue Type: Improvement (was: Sub-task)
> NUMA-awareness for separate join build
> --------------------------------------
>
> Key: IMPALA-9186
> URL: https://issues.apache.org/jira/browse/IMPALA-9186
> Project: IMPALA
> Issue Type: Improvement
> Components: Backend
> Reporter: Tim Armstrong
> Priority: Major
> Labels: multithreading
>
> 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
