You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Jaka Jaksic (JIRA)" <ji...@apache.org> on 2007/02/01 07:00:09 UTC
[jira] Created: (JCR-725) Configuration of CacheManager memory
sizes
Configuration of CacheManager memory sizes
------------------------------------------
Key: JCR-725
URL: https://issues.apache.org/jira/browse/JCR-725
Project: Jackrabbit
Issue Type: Improvement
Components: core
Affects Versions: 1.2.1
Reporter: Jaka Jaksic
Priority: Trivial
(I already posted this as comments under JCR-619.)
The maximum size for all caches in CacheManager is hardcoded to 16 megabytes and there's no way to change that. It would be nice if this as well as other CacheManager parameters were configurable. It's just a waste running Jackrabbit on a server with gigabytes of memory and only using 16 megabytes for cache...
I have created a really simple and straightforward patch (jackrabbit-cachemanager-config.patch) which enables reaching the CacheManager instance through RepositoryImpl object and setting all three of its memory parameters. The memory parameters are no longer static constants, but instance fields getting initial values from constants (so the default behavior of the class remains the same).
(It would be even nicer if these parameters were configurable via configuration files, but that should probably be implemented by someone close to the project.)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (JCR-725) Configuration of CacheManager memory
sizes
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting resolved JCR-725.
-------------------------------
Resolution: Fixed
Patch applied in revision 529894. Thanks!
> Configuration of CacheManager memory sizes
> ------------------------------------------
>
> Key: JCR-725
> URL: https://issues.apache.org/jira/browse/JCR-725
> Project: Jackrabbit
> Issue Type: Improvement
> Components: core
> Reporter: Jaka Jaksic
> Assigned To: Jukka Zitting
> Priority: Trivial
> Fix For: 1.3
>
> Attachments: jackrabbit-cachemanager-config.patch
>
>
> (I already posted this as comments under JCR-619.)
> The maximum size for all caches in CacheManager is hardcoded to 16 megabytes and there's no way to change that. It would be nice if this as well as other CacheManager parameters were configurable. It's just a waste running Jackrabbit on a server with gigabytes of memory and only using 16 megabytes for cache...
> I have created a really simple and straightforward patch (jackrabbit-cachemanager-config.patch) which enables reaching the CacheManager instance through RepositoryImpl object and setting all three of its memory parameters. The memory parameters are no longer static constants, but instance fields getting initial values from constants (so the default behavior of the class remains the same).
> (It would be even nicer if these parameters were configurable via configuration files, but that should probably be implemented by someone close to the project.)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (JCR-725) Configuration of CacheManager memory
sizes
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting updated JCR-725:
------------------------------
Fix Version/s: 1.3
Assignee: Jukka Zitting
Affects Version/s: (was: 1.2.1)
> Configuration of CacheManager memory sizes
> ------------------------------------------
>
> Key: JCR-725
> URL: https://issues.apache.org/jira/browse/JCR-725
> Project: Jackrabbit
> Issue Type: Improvement
> Components: core
> Reporter: Jaka Jaksic
> Assigned To: Jukka Zitting
> Priority: Trivial
> Fix For: 1.3
>
> Attachments: jackrabbit-cachemanager-config.patch
>
>
> (I already posted this as comments under JCR-619.)
> The maximum size for all caches in CacheManager is hardcoded to 16 megabytes and there's no way to change that. It would be nice if this as well as other CacheManager parameters were configurable. It's just a waste running Jackrabbit on a server with gigabytes of memory and only using 16 megabytes for cache...
> I have created a really simple and straightforward patch (jackrabbit-cachemanager-config.patch) which enables reaching the CacheManager instance through RepositoryImpl object and setting all three of its memory parameters. The memory parameters are no longer static constants, but instance fields getting initial values from constants (so the default behavior of the class remains the same).
> (It would be even nicer if these parameters were configurable via configuration files, but that should probably be implemented by someone close to the project.)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (JCR-725) Configuration of CacheManager memory
sizes
Posted by "Jaka Jaksic (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jaka Jaksic updated JCR-725:
----------------------------
Attachment: jackrabbit-cachemanager-config.patch
> Configuration of CacheManager memory sizes
> ------------------------------------------
>
> Key: JCR-725
> URL: https://issues.apache.org/jira/browse/JCR-725
> Project: Jackrabbit
> Issue Type: Improvement
> Components: core
> Affects Versions: 1.2.1
> Reporter: Jaka Jaksic
> Priority: Trivial
> Attachments: jackrabbit-cachemanager-config.patch
>
>
> (I already posted this as comments under JCR-619.)
> The maximum size for all caches in CacheManager is hardcoded to 16 megabytes and there's no way to change that. It would be nice if this as well as other CacheManager parameters were configurable. It's just a waste running Jackrabbit on a server with gigabytes of memory and only using 16 megabytes for cache...
> I have created a really simple and straightforward patch (jackrabbit-cachemanager-config.patch) which enables reaching the CacheManager instance through RepositoryImpl object and setting all three of its memory parameters. The memory parameters are no longer static constants, but instance fields getting initial values from constants (so the default behavior of the class remains the same).
> (It would be even nicer if these parameters were configurable via configuration files, but that should probably be implemented by someone close to the project.)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.