[
https://issues.apache.org/jira/browse/OAK-774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13651995#comment-13651995
]
Antonio Sanso commented on OAK-774:
-----------------------------------
Little update.
I am going to make the changes you suggested but in the meantime I have tried a
little benchmark with the current algorithm.
The use case is to invoke #getChildrenCount of one node with 1000 children
containing ACE with allow read (I know the use case is not a real life one but
it is a start).
# TreeTest min 10% 50% 90% max N
getChildrenCount 98 99 100 107 112 99
# TreeTest min 10% 50% 90% max N
getChildrenCount 0 0 0 1 6 58647
The first numbers are without the readstatus calculation while the second is
with the patch in place.
The numbers looks good to me :)
> Calculate readstatus
> --------------------
>
> Key: OAK-774
> URL: https://issues.apache.org/jira/browse/OAK-774
> Project: Jackrabbit Oak
> Issue Type: Sub-task
> Components: core, jcr
> Reporter: angela
> Assignee: angela
> Attachments: OAK-774-patch.txt, OAK-774-test-patch.txt,
> OAK-774-test-patch.txt
>
>
> this includes 2 major steps:
> - clarify meaning of ReadStatus.*_ALL in terms of reading access control
> content (and possibly extend the set of existing status)
> - implement calculation of read status in compiled permission impl
>
> the 2 things together will allow us to improve performance within the
> SecureNodeState for those trees where a given user has full access or
> at least full access to non-ac items.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
