jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vikas Saurabh (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-2779) DocumentNodeStore should provide option to set initial cache size as percentage of MAX VM size
Date Tue, 06 Dec 2016 11:11:23 GMT

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

Vikas Saurabh commented on OAK-2779:
------------------------------------

While I like the idea of a sane default that is useful in auto-config kind of way - but, I
wonder if treating heap size as fully available to oak based application is a correct assumption.
But, then, I think such applications (using same VM for multiple apps) are relatively less
in number and can configure this percentage or absolute value on their setups (this bearing
some pain for overall greater good :) ).

So, I think this is useful but would still like to tread with a bit caution.

> 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: documentmk
>    Affects Versions: 1.2
>            Reporter: Will McGauley
>              Labels: performance
>             Fix For: 1.8
>
>
> 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)

Mime
View raw message