Hummmm... I'm surprised. I expected the test to be unfair in favor of mysql for a simple graph traversal. In fact, i still think that with good mysql configuration and good sql tuning, mysql can be faster.
Of course, if you add different kind of relationship, node property, relationship property and complex query, i'm pretty sure that neo4j can be much much faster than any rdbms for querying graph based data :) (just think about the how many nested sql join you would need if you havenode/graph properties and many differents kind of relationship (eg : social network)) -- Ker2x On Tue, Mar 30, 2010 at 1:37 AM, Marko Rodriguez <[email protected]> wrote: > Hi guys, > > Sorry if you have already seen this (Twitter, Gremlin mailing list, etc.), > but for those that haven't, this is of potential interest to all you Neo4j > users. > > http://markorodriguez.com/Blarko/Entries/2010/3/29_MySQL_vs._Neo4j_on_a_Large-Scale_Graph_Traversal.html > > Take care, > Marko. > > http://markorodriguez.com > _______________________________________________ > Neo mailing list > [email protected] > https://lists.neo4j.org/mailman/listinfo/user > -- Laurent "ker2x" Laborde Sysadmin & DBA at http://www.over-blog.com/ _______________________________________________ Neo mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user
