[
https://issues.apache.org/jira/browse/BOOKKEEPER-578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13592528#comment-13592528
]
Matteo Merli commented on BOOKKEEPER-578:
-----------------------------------------
Yes, I've seen the buffers are read with NIO from disk so it makes sense to
direct buffers. The only thing, it's that using the default on 1/3 heap for
that is misleading, because one assumes that memory will be allocated from
inside the java heap. Say, if I configure the bookie jvm with -Xmx20g then the
total amount of memory that the jvm will be using is 27Gb (20 + 20*1/3).
> LedgerCacheImpl is reserving 1/3 of Heap size but allocates NonHeap memory
> --------------------------------------------------------------------------
>
> Key: BOOKKEEPER-578
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-578
> Project: Bookkeeper
> Issue Type: Bug
> Components: bookkeeper-server
> Reporter: Matteo Merli
> Priority: Minor
>
> By default the page limit parameter is set to -1, which means to assign 1/3
> of Heap space to the LedgerCache. Each LedgerEntryPage is then allocating the
> memory outside the heap (ByteBuffer.allocateDirect()).
> This makes BK to use more memory than the -XmxNN configured setting. Is there
> any particular reason for the LedgerEntryPage buffer to be allocated outside
> the java heap? Could that be changed?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
