[
https://issues.apache.org/jira/browse/IMPALA-5229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16831112#comment-16831112
]
Ruslan Dautkhanov commented on IMPALA-5229:
-------------------------------------------
Thank you for prompt response [~tarmstrong]
I agree it's hard to manage for Impala that's colocated with YARN and other
workloads for example.
It makes sense for some dedicated scenarios only .. we do use hugetlbfs on
dedicated Oracle servers for examples where we can tell exactly how much memory
Oracle will use for its caches etc.
> Try using TCMalloc + Huge Pages for buffers
> -------------------------------------------
>
> Key: IMPALA-5229
> URL: https://issues.apache.org/jira/browse/IMPALA-5229
> Project: IMPALA
> Issue Type: Improvement
> Components: Backend
> Affects Versions: Impala 2.9.0
> Reporter: Tim Armstrong
> Assignee: Tim Armstrong
> Priority: Major
> Labels: perf, resource-management
> Fix For: Impala 2.9.0
>
>
> As well as mmap() + huge pages, we could support TCMalloc + huge pages. I
> believe TCMalloc will support this well because:
> * We can allocate huge-page-aligned memory via posix_memalign()
> * TCMalloc, by default, always decommits large allocations upon freeing them.
> So if we undo the HUGEPAGE madvise() before handing the pages back to
> TCMalloc, then TCMalloc will decommit the huge pages backing the allocation,
> and we won't get TCMalloc's page heap into a weird state.
> This could give us the perf benefits of huge pages without some of the
> headaches associated with using mmap() directly.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
