Hi Gremlin+Neo4j+OrientDB people,
I apologize for the cross list posting, but this is an important piece of
information for those using Gremlin with their respective graph databases. I've
noticed lots of people use the very friendly notation of Element.key to get the
property value of an Element. Note that in Gremlin, this mapping from
Element.key to Element.getProperty(key) requires Java reflection and is a
costly operation. The cost of a pretty traversal expression is time. Please
read over this Wiki page for notes on optimizing your Gremlin queries:
https://github.com/tinkerpop/gremlin/wiki/Path-Optimizations
..especially the first section: "Avoid Element Property Selection using Key"
Finally, note that these times are with respect to Gremlin 1.3-SNAPSHOT which
will have a stable release September 21st.
Thanks so much and again, apologies for the cross post.
Marko.
http://markorodriguez.com
_______________________________________________
Neo4j mailing list
[email protected]
https://lists.neo4j.org/mailman/listinfo/user
