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 "Stefan Egli (JIRA)" <ji...@apache.org> on 2015/03/12 22:12:38 UTC

[jira] [Updated] (OAK-2622) dynamic cache allocation

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

Stefan Egli updated OAK-2622:
-----------------------------
    Description: 
At the moment mongoMk's various caches are configurable (OAK-2546) but other than that static in terms of size. Different use-cases might require different allocations of the sub caches though. And it might not always be possible to find a good configuration upfront for all use cases. 

We might be able to come up with dynamically allocating the overall cache size to the different sub-caches, based on which cache is how heavily loaded for example.

  was:
At the moment mongoMk's various caches are configurable (OAK-2546) but other than that static in terms of size. Different use-cases might require different allocations of the sub caches though. And it might not always be possible to find a good configuration upfront for all use cases. 

We might be able to come up with a dynamically allocating the overall cache size to the different sub-caches, based on which cache is how heavily loaded for example.


> dynamic cache allocation
> ------------------------
>
>                 Key: OAK-2622
>                 URL: https://issues.apache.org/jira/browse/OAK-2622
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: mongomk
>    Affects Versions: 1.0.12
>            Reporter: Stefan Egli
>             Fix For: 1.4
>
>
> At the moment mongoMk's various caches are configurable (OAK-2546) but other than that static in terms of size. Different use-cases might require different allocations of the sub caches though. And it might not always be possible to find a good configuration upfront for all use cases. 
> We might be able to come up with dynamically allocating the overall cache size to the different sub-caches, based on which cache is how heavily loaded for example.



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