jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Mueller (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-2745) PersistentCache should rely on eviction callback to add entry to the persistent cache
Date Wed, 22 Jul 2015 11:56:04 GMT

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

Thomas Mueller commented on OAK-2745:
-------------------------------------

Now the LIRS cache supports an eviction callback. That way, we can use additional metrics
to avoid persisting unnecessary entries (for example old revisions for the root node).

> PersistentCache should rely on eviction callback to add entry to the persistent cache
> -------------------------------------------------------------------------------------
>
>                 Key: OAK-2745
>                 URL: https://issues.apache.org/jira/browse/OAK-2745
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: mongomk
>            Reporter: Chetan Mehrotra
>            Assignee: Thomas Mueller
>              Labels: performance
>             Fix For: 1.3.4
>
>
> Currently when PersistentCache is enabled then any put results in addition of the entry
to in memory cache and also to the backing persistent cache. While adding the entry to the
persistent cache there is slight overhead of serialization of the entry to be paid.
> To avoid such overheads at time of read/write to in memory cache it would be better to
move the logic to separate thread. PersistentCache can make use of Guava cache eviction callback
and then add the entry to the backend persistent store



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message