[
https://issues.apache.org/jira/browse/ARROW-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16223332#comment-16223332
]
Uwe L. Korn commented on ARROW-1733:
------------------------------------
I'm not sure if this is really a good approach. By keeping the allocations
separate, the allocator can ensure that the start of each allocation also is a
start of a page. By separating them, we might get performance regressions by
having non-page aligned memory for large allocations. Probably having some
offset, e.g. size(bitmap) + size(payload) < 8k, could be a solution. Smaller
allocations are done at once, larger ones separate. In the end this is all
guessing for now, we should test!
> [C++] Utility for allocating fixed-size mutable primitive ArrayData with a
> single memory allocation
> ---------------------------------------------------------------------------------------------------
>
> Key: ARROW-1733
> URL: https://issues.apache.org/jira/browse/ARROW-1733
> Project: Apache Arrow
> Issue Type: New Feature
> Components: C++
> Reporter: Wes McKinney
>
> The validity bitmap and the values for the primitive data would be part of a
> single allocation, so better heap locality and possibly better performance in
> aggregate. This same approach is also being worked on for Java
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
