[
https://issues.apache.org/jira/browse/TINKERPOP3-957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15006889#comment-15006889
]
ASF GitHub Bot commented on TINKERPOP3-957:
-------------------------------------------
Github user twilmes commented on the pull request:
https://github.com/apache/incubator-tinkerpop/pull/144#issuecomment-157090801
One thought I had was to create a new discovery type ticket to go in and do
a more thorough analysis across a wider range of traversal uses to pull out
other areas we can make similar improvements that will decrease traversal
execution overhead. That could then lead to some specific, targeted tickets.
> Improve speed of addV()
> -----------------------
>
> Key: TINKERPOP3-957
> URL: https://issues.apache.org/jira/browse/TINKERPOP3-957
> Project: TinkerPop 3
> Issue Type: Improvement
> Components: process
> Affects Versions: 3.0.2-incubating
> Reporter: stephen mallette
> Assignee: Marko A. Rodriguez
> Fix For: 3.1.1-incubating
>
> Attachments: addVBaseline.svg
>
>
> The performance gap between {{GraphTraversalSource.addV()}} and
> {{Graph.addVertex()}} is fairly wide:
> {code}
> gremlin> testAddV = { num -> graph = TinkerGraph.open(); g =
> graph.traversal(); for (i = 0; i < num; i++) { g.addV(id, i).next() } }
> ==>groovysh_evaluate$_run_closure1@30b9eadd
> gremlin> testAddVertex = { num -> graph = TinkerGraph.open(); for (i = 0; i
> < num; i++) { graph.addVertex(id, i) } }
> ==>groovysh_evaluate$_run_closure1@2e647e59
> gremlin> clock {testAddV(100000)}
> ==>462.04376528
> gremlin> clock {testAddVertex(100000)}
> ==>70.90365949999999
> {code}
> Try to make some improvements there. Perhaps this work should also extend to
> {{addE/addEdge}} as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
