Updated conclusions about the graph database benchmark – Neo4j can perform much better by Alex Popescu.
You may recall in Benchmarking Graph Databases I reported on a comparison of Neo4j against three relational databases, MySQL, Vertica and VoltDB.
Alex has listed resources relevant to the response from the original testers:
Our conclusions from this are that, like any of the complex systems we tested, properly tuning Neo4j can be tricky and getting optimal performance may require some experimentation with parameters. Whether a user of Neo4j can expect to see runtimes on graphs like this measured in milliseconds or seconds depends on workload characteristics (warm / cold cache) and whether setup steps can be amortized across many queries or not.
The response, Benchmarking Graph Databases – Updates, shows that Neo4j on shortest path outperforms MySQL, Vertica and VoltDB.
But scores on shortest path don’t appear for MySQL, Vertica and VoltDB on shortest path in the “Updates” post.
Let me help you with that.
Here is the original comparison:
Here is Neo4j shortest path after reading the docs and suggestions from Neo4j tech support:
First graph has time in seconds, second graph has time in milliseconds.
Set up correctly, measure milliseconds on shortest path for Neo4j. SQL solutions, well, the numbers speak for themselves.
The moral here is to read software documentation and contact tech support before performing and publishing benchmarks.