[jira] [Commented] (ARROW-1627) [JAVA] Reduce heap usage(Phase 2) - memory footprint in AllocationManager.BufferLedger

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ARROW-1627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16269987#comment-16269987 ] 

ASF GitHub Bot commented on ARROW-1627:
---------------------------------------

sadikovi commented on issue #1150: ARROW-1627: New class to handle collection of BufferLedger(s) within …
URL: https://github.com/apache/arrow/pull/1150#issuecomment-347735233
 
 
   @wesm Should it be `LowCostIdentityHasMap` -> `LowCostIdentityHashMap`?

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> [JAVA] Reduce heap usage(Phase 2) - memory footprint in AllocationManager.BufferLedger
> --------------------------------------------------------------------------------------
>
>                 Key: ARROW-1627
>                 URL: https://issues.apache.org/jira/browse/ARROW-1627
>             Project: Apache Arrow
>          Issue Type: Improvement
>          Components: Java - Memory
>            Reporter: Yuliya Feldman
>            Assignee: Yuliya Feldman
>              Labels: pull-request-available
>             Fix For: 0.8.0
>
>
> Currently we instantiate IdentityHashMap while creating an instance of AllocationManager which is in turn is part of BufferLedger
> By default IdentityHashMap allocates an array of 64 objects which is 272 bytes of heap from the start. In reality a lot of ArrowBuf(s) will not need that many entries in the map, since they want share BufferAllocators with many other BufferLedgers.
> Suggestion is to come up with different collection to save heap w/o sacrificing much of the performance (if any).
> I have a suggestion in mind that I will share via a doc. later today



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)