jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "angela (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (JCR-2943) UserManagement: membership cache default size too small
Date Thu, 14 Apr 2011 10:56:06 GMT

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

angela resolved JCR-2943.

    Resolution: Fixed

use the growing lru map functionality used by michael in the ac evaluation.
however, i didn't add additional debug information since the node identifier didn't
seem to be useful from my point of view.

> UserManagement: membership cache default size too small
> -------------------------------------------------------
>                 Key: JCR-2943
>                 URL: https://issues.apache.org/jira/browse/JCR-2943
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-core, security
>    Affects Versions: 2.2.0, 2.2.1, 2.2.2, 2.2.4
>         Environment: Repository with users being member of over 150 groups
>            Reporter: Honwai Wong
>            Assignee: angela
>             Fix For: 2.3.0
> The membership cache that has been introduced in JCR-2703 is making use of an LRUMap
to cache group memberships (authorizable nodeId -> group nodeIds). In environments where
users belong to more than 100 groups, the cache quickly becomes ineffective due to the default
maximum size of the LRUMap.
> Once the cache limit is hit, the rather expensive Node#getWeakReferences API calls resulting
in search queries are executed again, leading to quite noticeable performance drops. Thus
I'd suggest to either make the membership cache configurable or introduce some logic to let
the cache grow dynamically as needed (still having some kind of hard limit to avoid memory

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message