[
https://issues.apache.org/jira/browse/BOOKKEEPER-578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13595498#comment-13595498
]
Rakesh R commented on BOOKKEEPER-578:
-------------------------------------
bq.we could make the 'pages' cache bounded and also feel to use normal
bytebuffers.
oops! I haven't seen the (pageCount < pageLimit) logic, its efficiently sizing
the cache. As I understand, directbuffers can be used in areas where native I/O
interaction happens. Usually its recommended to use direct buffers for large,
long-lived buffers that are subject to the underlying system's native I/O
operations.
> 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
