> I think the only way to do this objectively is to have a test and then give each DB vendor an opportunity to tweak the DB and queries to optimize performance.
AFAIK they are: the test is open source, the raw results are there, and contributions welcomed. Hopefully the OrientDB team will step up and show how theirs can perform.
Hey all, we sent a Pull Request 2 days ago to the author of the Benchmark, as they used OrientDB incorrectly. Now OrientDB is the fastest in all the benchmarks, except for "singleRead" and "neighbors2", but we know why.
We are still waiting for the Arango team to update the results...
> Hey all, we sent a Pull Request 2 days ago [...] We are still waiting for the Arango team to update the results...
Let's see:
1. You sent it at the weekend
2. The Arango team have a life
3. It took you 9 days to send the PR
4. The start of the week always is busy, regardless of which company you work at...
Give over and stop trying to make out there is something suspicious in whatever the Arango team do. It makes you (look like) a jerk.
Lvca, good to see the OrientDB team cooperating in the benchmark. Performance is just one aspect when evaluating a database, other things like robustness, stability, community can be as important if not more important. As such as I’ve shared my 10 month experience with OrientDB in:
http://orientdbleaks.blogspot.com/2015/06/the-orientdb-issue...
AFAIK they are: the test is open source, the raw results are there, and contributions welcomed. Hopefully the OrientDB team will step up and show how theirs can perform.