[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.8) > 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 > > 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.4.14#64029)
[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 ] Chetan Mehrotra updated OAK-2779: - Fix Version/s: 1.8 > 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)
[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 ] Chetan Mehrotra updated OAK-2779: - Component/s: (was: mongomk) documentmk > 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)
[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: -- Labels: performance (was: performance resilience) > 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 > Labels: performance > > 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)
[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.3.9) > 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 > Labels: performance, resilience > > 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)
[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 ] Amit Jain updated OAK-2779: --- Fix Version/s: (was: 1.3.7) 1.3.8 > 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 > Labels: performance, resilience > Fix For: 1.3.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)
[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 ] Michael Marth updated OAK-2779: --- Labels: performance resilience (was: ) 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 Labels: performance, resilience Fix For: 1.3.5 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)
[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 ] Davide Giannella updated OAK-2779: -- Fix Version/s: (was: 1.3.4) 1.3.5 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.5 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)
[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 ] Davide Giannella updated OAK-2779: -- Fix Version/s: (was: 1.3.3) 1.3.4 Bulk move to 1.3.4 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.4 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)
[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 ] Davide Giannella updated OAK-2779: -- Fix Version/s: (was: 1.3.2) 1.3.3 Bulk move to 1.3.3. 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.3 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)
[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 ] Davide Giannella updated OAK-2779: -- Fix Version/s: (was: 1.3.1) 1.3.2 Bulk move to 1.3.2 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.2 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)
[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 ] Davide Giannella updated OAK-2779: -- Fix Version/s: (was: 1.3.0) 1.3.1 Bulk move to 1.3.1 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.1 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)
[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)