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/04/16 14:43:59 UTC

[jira] [Updated] (OAK-2779) DocumentNodeStore should provide option to set initial cache size as percentage of MAX VM size

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

Marcel Reutegger updated OAK-2779:
----------------------------------
    Fix Version/s:     (was: 1.2.1)
                   1.3.0

> DocumentNodeStore should provide option to set initial cache size as percentage of MAX VM size
> ----------------------------------------------------------------------------------------------
>
>                 Key: OAK-2779
>                 URL: https://issues.apache.org/jira/browse/OAK-2779
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: mongomk
>    Affects Versions: 1.2
>            Reporter: Will McGauley
>             Fix For: 1.3.0
>
>
> Currently the DocumentNodeStore provides a way to configure various cache parameters, including cache size and distribution of that size to various caches.  The distribution of caches is done as a % of the total cache size, which is very helpful, but the overall cache size can only be set as a literal value.
> It would be helpful to achieve a good default value based on the available VM memory as a %, instead of a literal value.  By doing this the cache size would not need to be set by each customer, and a better initial experience would be achieved.  
> I suggest that 25% of the max VM size would be a good starting point.



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