jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Dürig (JIRA) <j...@apache.org>
Subject [jira] [Commented] (OAK-4635) Improve cache eviction policy of the node deduplication cache
Date Wed, 03 Aug 2016 09:18:20 GMT

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

Michael Dürig commented on OAK-4635:

At https://github.com/mduerig/jackrabbit-oak/commit/58b637f67b6ff289aab022609d598efd91139765
I implemented and alternative cache eviction strategy, which just removes one random element
from the deepest level instead of fully clearing it. 

> Improve cache eviction policy of the node deduplication cache
> -------------------------------------------------------------
>                 Key: OAK-4635
>                 URL: https://issues.apache.org/jira/browse/OAK-4635
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: segment-tar
>            Reporter: Michael Dürig
>            Assignee: Michael Dürig
>              Labels: perfomance
>             Fix For: Segment Tar 1.0.0
> {{NodeCache}} uses one stripe per depth (of the nodes in the tree). Once its overall
capacity (default 1000000 nodes) is exceeded, it clears all nodes from the stripe with the
greatest depth. This can be problematic when the stripe with the greatest depth contains most
of the nodes as clearing it would result in an almost empty cache. 

This message was sent by Atlassian JIRA

View raw message