[
https://issues.apache.org/jira/browse/RANGER-4922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892233#comment-17892233
]
Abhay Kulkarni commented on RANGER-4922:
----------------------------------------
Additional commit details:
master:
https://github.com/apache/ranger/commit/dfd57ff5208d7811cf05e689a986f728152ff8b1
> Reduce time to find tags associated with multi-level resource
> -------------------------------------------------------------
>
> Key: RANGER-4922
> URL: https://issues.apache.org/jira/browse/RANGER-4922
> Project: Ranger
> Issue Type: Improvement
> Components: Ranger
> Reporter: Abhay Kulkarni
> Assignee: Abhay Kulkarni
> Priority: Major
> Fix For: 3.0.0, 2.6.0
>
>
> With the following use case:
> * Service supports resource hierarchy with more than one level
> * Large number of tags are associated with the resources, with majority of
> tagged resources with values for all levels in resource hierarchy
> * Accessed resource does not have values for all levels in the resource
> hierarchy
> the time required to find the tags associated with the accessed resource is
> significant.
> When tested with a large number of tagged Ozone resources (~ 629,000) with
> approximately 20 tagged volumes and 103 tagged buckets and the rest being
> keys, the access evaluation times are:
> {code:java}
> (volume, bucket, key) : requestCount=629118, avgTimeTaken=49911ns
> (volume, bucket) : requestCount=103, avgTimeTaken=10738069ns
> (volume) :
> - requestCount=20, avgTimeTaken=21968890ns
> - requestCount=1056, avgTimeTaken=13763978ns (repeated requests in previous
> run multiple times) {code}
> This patch, using filtering and caching technique attempts to reduce this
> time.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
