You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Julian Reschke (Created) (JIRA)" <ji...@apache.org> on 2012/03/08 15:59:57 UTC
[jira] [Created] (JCR-3254) make max size of
CachingEntryCollector's cache configurable
make max size of CachingEntryCollector's cache configurable
-----------------------------------------------------------
Key: JCR-3254
URL: https://issues.apache.org/jira/browse/JCR-3254
Project: Jackrabbit Content Repository
Issue Type: Sub-task
Components: jackrabbit-core
Affects Versions: 2.4, 2.2.11
Reporter: Julian Reschke
Assignee: Julian Reschke
Priority: Minor
Fix For: 2.2.12, 2.4.1, 2.6
To assist in analyzing the bottleneck it would be good if it was easy to change the max size, currently hard-wired to 5000. Suggest to be pragmatic and do that through a system property.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (JCR-3254) make max size of
CachingEntryCollector's cache configurable
Posted by "Jan Haderka (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-3254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13506300#comment-13506300 ]
Jan Haderka commented on JCR-3254:
----------------------------------
Could you shed some light on "the problem" and it's symptoms? Or at least link the post in userlist related to this.
Thx.
> make max size of CachingEntryCollector's cache configurable
> -----------------------------------------------------------
>
> Key: JCR-3254
> URL: https://issues.apache.org/jira/browse/JCR-3254
> Project: Jackrabbit Content Repository
> Issue Type: Sub-task
> Components: jackrabbit-core
> Affects Versions: 2.2.11, 2.4
> Reporter: Julian Reschke
> Assignee: Julian Reschke
> Priority: Minor
> Fix For: 2.2.12, 2.4.1, 2.5
>
>
> To assist in analyzing the bottleneck it would be good if it was easy to change the max size, currently hard-wired to 5000. Suggest to be pragmatic and do that through a system property.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (JCR-3254) make max size of
CachingEntryCollector's cache configurable
Posted by "Jan Haderka (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-3254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13506324#comment-13506324 ]
Jan Haderka commented on JCR-3254:
----------------------------------
Oops. Missed the fact it was subtask. Thx.
> make max size of CachingEntryCollector's cache configurable
> -----------------------------------------------------------
>
> Key: JCR-3254
> URL: https://issues.apache.org/jira/browse/JCR-3254
> Project: Jackrabbit Content Repository
> Issue Type: Sub-task
> Components: jackrabbit-core
> Affects Versions: 2.2.11, 2.4
> Reporter: Julian Reschke
> Assignee: Julian Reschke
> Priority: Minor
> Fix For: 2.2.12, 2.4.1, 2.5
>
>
> To assist in analyzing the bottleneck it would be good if it was easy to change the max size, currently hard-wired to 5000. Suggest to be pragmatic and do that through a system property.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (JCR-3254) make max size of
CachingEntryCollector's cache configurable
Posted by "angela (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-3254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13225263#comment-13225263 ]
angela commented on JCR-3254:
-----------------------------
while i agree that it was useful for problem analysis, i somehow dislike the idea of having the size configurable with the acprovider config.
the main reason is that i wouldn't want to be stuck with that implementation which imo has some fundamental drawbacks (e.g. perm eval
only calculated on access).
using a system property for analysis was fine for me if it was not part of an official release but only some sort of analysis-patch that
is used temporarily.
> make max size of CachingEntryCollector's cache configurable
> -----------------------------------------------------------
>
> Key: JCR-3254
> URL: https://issues.apache.org/jira/browse/JCR-3254
> Project: Jackrabbit Content Repository
> Issue Type: Sub-task
> Components: jackrabbit-core
> Affects Versions: 2.2.11, 2.4
> Reporter: Julian Reschke
> Assignee: Julian Reschke
> Priority: Minor
> Fix For: 2.2.12, 2.4.1, 2.6
>
>
> To assist in analyzing the bottleneck it would be good if it was easy to change the max size, currently hard-wired to 5000. Suggest to be pragmatic and do that through a system property.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (JCR-3254) make max size of
CachingEntryCollector's cache configurable
Posted by "Julian Reschke (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-3254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13225276#comment-13225276 ]
Julian Reschke commented on JCR-3254:
-------------------------------------
I think once we understand the problem fully, and have a fix we can just nuke the system property. So it's really temporary.
> make max size of CachingEntryCollector's cache configurable
> -----------------------------------------------------------
>
> Key: JCR-3254
> URL: https://issues.apache.org/jira/browse/JCR-3254
> Project: Jackrabbit Content Repository
> Issue Type: Sub-task
> Components: jackrabbit-core
> Affects Versions: 2.2.11, 2.4
> Reporter: Julian Reschke
> Assignee: Julian Reschke
> Priority: Minor
> Fix For: 2.2.12, 2.4.1, 2.6
>
>
> To assist in analyzing the bottleneck it would be good if it was easy to change the max size, currently hard-wired to 5000. Suggest to be pragmatic and do that through a system property.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (JCR-3254) make max size of
CachingEntryCollector's cache configurable
Posted by "Julian Reschke (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-3254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13506323#comment-13506323 ]
Julian Reschke commented on JCR-3254:
-------------------------------------
Jan: see the parent issue JCR-2950
> make max size of CachingEntryCollector's cache configurable
> -----------------------------------------------------------
>
> Key: JCR-3254
> URL: https://issues.apache.org/jira/browse/JCR-3254
> Project: Jackrabbit Content Repository
> Issue Type: Sub-task
> Components: jackrabbit-core
> Affects Versions: 2.2.11, 2.4
> Reporter: Julian Reschke
> Assignee: Julian Reschke
> Priority: Minor
> Fix For: 2.2.12, 2.4.1, 2.5
>
>
> To assist in analyzing the bottleneck it would be good if it was easy to change the max size, currently hard-wired to 5000. Suggest to be pragmatic and do that through a system property.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (JCR-3254) make max size of
CachingEntryCollector's cache configurable
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-3254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting updated JCR-3254:
-------------------------------
Fix Version/s: (was: 2.6)
2.5
> make max size of CachingEntryCollector's cache configurable
> -----------------------------------------------------------
>
> Key: JCR-3254
> URL: https://issues.apache.org/jira/browse/JCR-3254
> Project: Jackrabbit Content Repository
> Issue Type: Sub-task
> Components: jackrabbit-core
> Affects Versions: 2.2.11, 2.4
> Reporter: Julian Reschke
> Assignee: Julian Reschke
> Priority: Minor
> Fix For: 2.2.12, 2.4.1, 2.5
>
>
> To assist in analyzing the bottleneck it would be good if it was easy to change the max size, currently hard-wired to 5000. Suggest to be pragmatic and do that through a system property.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (JCR-3254) make max size of
CachingEntryCollector's cache configurable
Posted by "Julian Reschke (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-3254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julian Reschke resolved JCR-3254.
---------------------------------
Resolution: Fixed
> make max size of CachingEntryCollector's cache configurable
> -----------------------------------------------------------
>
> Key: JCR-3254
> URL: https://issues.apache.org/jira/browse/JCR-3254
> Project: Jackrabbit Content Repository
> Issue Type: Sub-task
> Components: jackrabbit-core
> Affects Versions: 2.2.11, 2.4
> Reporter: Julian Reschke
> Assignee: Julian Reschke
> Priority: Minor
> Fix For: 2.2.12, 2.4.1, 2.6
>
>
> To assist in analyzing the bottleneck it would be good if it was easy to change the max size, currently hard-wired to 5000. Suggest to be pragmatic and do that through a system property.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira