You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "angela (JIRA)" <ji...@apache.org> on 2016/11/22 17:47:58 UTC

[jira] [Resolved] (OAK-5025) Speed up ACE node name generation

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

angela resolved OAK-5025.
-------------------------
       Resolution: Fixed
    Fix Version/s: 1.5.15

Committed revision 1770863.


> Speed up ACE node name generation
> ---------------------------------
>
>                 Key: OAK-5025
>                 URL: https://issues.apache.org/jira/browse/OAK-5025
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 1.5.12
>            Reporter: Alex COLLIGNON
>            Assignee: angela
>            Priority: Minor
>              Labels: performance
>             Fix For: 1.6, 1.5.15
>
>         Attachments: OAK-5025-ACE-name-generation-benchmarks.patch, OAK-5025-ACE-random-nodename-generation.patch, ace_creation_index.txt, ace_creation_index_withsave.txt, ace_creation_random.txt, ace_creation_random_withsave.txt, ace_creation_status_quo.txt, ace_creation_status_quo_withsave.txt
>
>
> Currently, {{o.a.j.oak.security.authorization.accesscontrol.Util#generateAceName}} is traversing all the existing ACE of a certain node in order to generate continuous numbering (allow0, allow1, allow2).
> While that certainly helps to produce human readable names, it represents quite a performance bottleneck when the number of existing ACE starts to grow.
> Since the naming is a pure implementation detail, my proposal is to keep the continuous numbering for the first hundreds of nodes and then use a random number to generate unique names in a faster fashion.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)