You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Shawn McKinney (Jira)" <ji...@apache.org> on 2022/01/03 20:20:00 UTC

[jira] [Created] (FC-307) Performance problem with roles many members

Shawn McKinney created FC-307:
---------------------------------

             Summary: Performance problem with roles many members 
                 Key: FC-307
                 URL: https://issues.apache.org/jira/browse/FC-307
             Project: FORTRESS
          Issue Type: Improvement
    Affects Versions: 2.0.7
            Reporter: Shawn McKinney
            Assignee: Shawn McKinney
             Fix For: 2.0.8


This issue brings performance improvements to situations where the role.occupants is enabled on role entries.  The problem, is groups with many members can be costly to update and even read.  Insertions are slow because large groups are expensive in LDAP.  There are mitigating factors on the server side that are beyond the scope of this discussion.

Reads are slow, because pulling entries back with 1000's even hundreds of thousand members is actually pulling a bunch of data across.  So, what we can do, is only pull back the members when absolutely necessary.

This issue addresses this by adding a method to the RoleP and RoleDAO classes called readConstraints.  It only pulls back the constraints and parents on the entry.  

This method replaces the role validation, constraint and hierarchical processing that occurs in the AdminMgrImpl class.




--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@directory.apache.org
For additional commands, e-mail: dev-help@directory.apache.org