[
https://issues.apache.org/jira/browse/ATLAS-3563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16998804#comment-16998804
]
ASF subversion and git services commented on ATLAS-3563:
--------------------------------------------------------
Commit db467ed60ed9537be8cad258322bea9f2e53f3f9 in atlas's branch
refs/heads/branch-2.0 from Sarath Subramanian
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=db467ed ]
ATLAS-3563: Improve tag propagation performance using in-memory traversal
(cherry picked from commit 7423addb220330cceadbf690d3bf4e4e5fcde99f)
> Improve tag propagation performance using in-memory traversal
> -------------------------------------------------------------
>
> Key: ATLAS-3563
> URL: https://issues.apache.org/jira/browse/ATLAS-3563
> Project: Atlas
> Issue Type: Task
> Components: atlas-core
> Affects Versions: 2.0.0
> Reporter: Sarath Subramanian
> Assignee: Sarath Subramanian
> Priority: Major
> Fix For: 2.1.0
>
>
> Tag propagation uses gremlin query to find entities to which the tag has to
> be propagated to.
> Gremlin query doesn't scale well for entities with large lineage (with many
> depth). In-memory traversal seems to have improved performance significantly
> since it avoids the overhead added by gremlin script engine initialization,
> query execution time.
> Performance improvement in tag propagation from *3004 ms* to *180 ms* is seen
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
