[
https://issues.apache.org/jira/browse/OAK-2745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella updated OAK-2745:
----------------------------------
Fix Version/s: (was: 1.3.2)
1.3.3
Bulk move to 1.3.3.
> 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.3
>
>
> 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)
