[jira] [Updated] (ATLAS-3563) Improve tag propagation performance using in-memory traversal
[ https://issues.apache.org/jira/browse/ATLAS-3563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sarath Subramanian updated ATLAS-3563: -- Description: 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 was: Tag propagation uses gremlin query to find entities to which the tag has to be propagated to. Gremlin query is not scaling 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 > 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)
[jira] [Updated] (ATLAS-3563) Improve tag propagation performance using in-memory traversal
[ https://issues.apache.org/jira/browse/ATLAS-3563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sarath Subramanian updated ATLAS-3563: -- Attachment: (was: ATLAS-3563.001.patch) > 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 is not scaling 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)
[jira] [Updated] (ATLAS-3563) Improve tag propagation performance using in-memory traversal
[ https://issues.apache.org/jira/browse/ATLAS-3563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sarath Subramanian updated ATLAS-3563: -- Attachment: ATLAS-3563.001.patch > 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 > > Attachments: ATLAS-3563.001.patch > > > Tag propagation uses gremlin query to find entities to which the tag has to > be propagated to. > Gremlin query is not scaling 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)
