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 2015/07/16 10:33:04 UTC

[jira] [Commented] (OAK-3112) Performance degradation of UnsavedModifications on MapDB

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

Marcel Reutegger commented on OAK-3112:
---------------------------------------

This only affects the 1.0 branch where MapDB was introduced with OAK-1768. For 1.2 the dependency was removed again with OAK-2131.

> Performance degradation of UnsavedModifications on MapDB
> --------------------------------------------------------
>
>                 Key: OAK-3112
>                 URL: https://issues.apache.org/jira/browse/OAK-3112
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: core, mongomk
>    Affects Versions: 1.0.7, 1.0.8, 1.0.9, 1.0.10, 1.0.11, 1.0.12, 1.0.13, 1.0.14, 1.0.15, 1.0.16, 1.0.17
>            Reporter: Marcel Reutegger
>            Assignee: Marcel Reutegger
>             Fix For: 1.0.18
>
>
> UnsavedModifications performance degrades when used in combination with the MapDB backed MapFactory. Calls become more and more expensive the longer the instance is in use. The is caused by a limitation of MapDB, which does not remove empty BTree nodes.
> A test performed with random paths added to the map and later removed again in a loop shows a increase to roughly 1 second to read keys present in the map when the underlying data file is about 50MB in size.



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