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 2016/02/16 11:52:18 UTC

[jira] [Resolved] (OAK-2745) PersistentCache should rely on eviction callback to add entry to the persistent cache

     [ https://issues.apache.org/jira/browse/OAK-2745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marcel Reutegger resolved OAK-2745.
-----------------------------------
       Resolution: Duplicate
    Fix Version/s: OAK-2761

Resolving as duplicate of OAK-2761. The implementation of OAK-2761 uses the eviction callback to persist data in a background thread.

> 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: OAK-2761
>
>
> 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)