[ http://issues.apache.org/jira/browse/JCR-619?page=all ]
Thomas Mueller updated JCR-619:
-------------------------------
Attachment: cacheManager5.txt
Hi,
This is the latest version of the CacheManager.
As the CacheManager is not a singleton any more, the problem JCR-625 (Memory is
not freed up when redeployed) should not appear with this patch.
Also, the performance degradation found with the earlier versions of the
CacheManager should be solved (now the caches are removed from the CacheManager
when the session is closed). This has been tested with the unit tests so far on
two machines.
Thomas
> CacheManager (Memory Management in Jackrabbit)
> ----------------------------------------------
>
> Key: JCR-619
> URL: http://issues.apache.org/jira/browse/JCR-619
> Project: Jackrabbit
> Issue Type: New Feature
> Components: core
> Affects Versions: 1.1
> Reporter: Thomas Mueller
> Assigned To: Tobias Bocanegra
> Fix For: 1.2
>
> Attachments: cacheManager.txt, cacheManager2.txt, cacheManager5.txt
>
>
> Jackrabbit can run out of memory because the the combined size of the various
> caches is not managed. The biggest problem (for me) is the combined size of
> the o.a.j.core.state.MLRUItemStateCache caches. Each session seems to create
> a few (?) of those caches, and each one is limited to 4 MB by default.
> I have implemented a dynamic (cache-) memory management service that
> distributes a fixed amount of memory dynamically to all those caches.
> Here is the patch
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
