[
https://issues.apache.org/jira/browse/OAK-7469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16462829#comment-16462829
]
Alex Deparvu commented on OAK-7469:
-----------------------------------
bq. did you also run the dynamic membership for comparison of the numbers?
I did a few inconclusive test runs. the patch changes a method that is
effectively not called while enabling the dynamic membership so it should have
no impact there. Comparing (trunk+ dynamic membership) with (patch) seems the
former comes up on top (something like 10% faster), and in any case enabling
the dynamic membership should be the way to go forward, the patch would only
help if running the old code.
> User membership synchronization could skip updating groups the user is
> already part of
> ---------------------------------------------------------------------------------------
>
> Key: OAK-7469
> URL: https://issues.apache.org/jira/browse/OAK-7469
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: auth-external, security
> Reporter: Alex Deparvu
> Assignee: Alex Deparvu
> Priority: Major
> Fix For: 1.10
>
> Attachments: OAK-7469.patch
>
>
> Currently the user group membership sync process doesn't take into account
> what groups the user is already a part of, so it will update all groups
> information by adding the user. we can skip this step based on group
> information on the user.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
