You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Marcel Reutegger (JIRA)" <ji...@apache.org> on 2013/08/21 14:10:51 UTC

[jira] [Commented] (OAK-969) More accurate cache weight for Segment

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

Marcel Reutegger commented on OAK-969:
--------------------------------------

Turns out this may get even worse. Now I'm looking at a dump where the cache is set to 64MB and the retained set is 300MB.

Some stats:
- The dump contains 21'411 Segment instances.
- The smallest Segments have a retained size of 336 bytes and a ByteBuffer limit of 4.
- The largest Segment has a retained size of 90k and a ByteBuffer limit of 65600.
- The average retained size of a Segment is 14k

This is the main contributor to the OOME reported in OAK-968.
                
> More accurate cache weight for Segment
> --------------------------------------
>
>                 Key: OAK-969
>                 URL: https://issues.apache.org/jira/browse/OAK-969
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core
>            Reporter: Marcel Reutegger
>            Priority: Minor
>
> The cache weight for the Segment currently only takes the size of the ByteBuffer into account. A heap dump showed that with a cache size of 100MB the actual memory usage was roughly 170MB.

--
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