[
https://issues.apache.org/jira/browse/ARROW-15758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17496941#comment-17496941
]
Antoine Pitrou commented on ARROW-15758:
----------------------------------------
This sounds like a good idea to me.
> [C++] Explore upgrading to mimalloc V2
> --------------------------------------
>
> Key: ARROW-15758
> URL: https://issues.apache.org/jira/browse/ARROW-15758
> Project: Apache Arrow
> Issue Type: Improvement
> Components: C++
> Affects Versions: 7.0.0
> Reporter: Will Jones
> Priority: Major
>
> ARROW-15730 found that mimalloc wasn't releasing memory as expected. These
> memory allocators tend to hold onto memory longer than users expect, which
> can be confusing. But also there appears to be [a bug where it also doesn't
> reuse
> memory|https://github.com/microsoft/mimalloc/issues/383#issuecomment-846132613].
> Both of these are addressed in v2.0.X (beta) of the library: the allocation
> is more aggressive in returning memory and the bug seems to not exist.
> [According to one of the
> maintainers|https://github.com/microsoft/mimalloc/issues/466#issuecomment-947819685],
> the main reason 2.0.X hasn't been declared stable is that some use cases
> have reported performance regressions. We could create a branch of Arrow
> using mimalloc v2 and run conbench benchmarks to see comparisons. If it's
> faster, we may consider moving forward; if not, we could provide feedback to
> the mimalloc maintainers which may help development along.
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
