[
https://issues.apache.org/jira/browse/ARROW-3243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16616839#comment-16616839
]
Wes McKinney commented on ARROW-3243:
-------------------------------------
Well, it needs to include the patch that we slaved over, resulting in a
vendored specific private version of jemalloc. Otherwise I don't see an issue
> [C++] Upgrade jemalloc to version 5
> -----------------------------------
>
> Key: ARROW-3243
> URL: https://issues.apache.org/jira/browse/ARROW-3243
> Project: Apache Arrow
> Issue Type: Improvement
> Reporter: Philipp Moritz
> Priority: Major
>
> Is it possible/feasible to upgrade jemalloc to version 5 and assume that
> version? I'm asking because I've been working towards replacing dlmalloc in
> plasma with jemalloc, which makes some of the code much nicer and removes
> some of the issues we had with dlmalloc, but it requires jemalloc APIs that
> are only available starting from jemalloc version 5, in particular, I'm using
> the extent_hooks_t capability.
> For now I can submit a patch that uses a different version of jemalloc in
> plasma and then we can figure out how to deal with it (maybe there is a way
> to make it work with older versions). What are your thoughts?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
