[
https://issues.apache.org/jira/browse/ARROW-3243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16621971#comment-16621971
]
Uwe L. Korn commented on ARROW-3243:
------------------------------------
The patch we have is solely relevant for jemalloc-4, it was already in the
released jemalloc-5 branch. Sadly jemalloc 5 had some changes that made it
unusable in the {{manylinux1}} setting. It could be that these are resolved,
then we could switch to a newer version. You can simply try this by changing
the installation script. Otherwise we probably have to wait until we have
changed our wheel to be based on {{manylinux2010}}.
> [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)
