nosql-tests

True, benchmarking is really not trivial. Thanks for pointing us to the bug in our benchmark suite and sorry for our mistake. We fixed it https://github.com/weinberger/nosql-tests/pull/24 and reran the benchmark. We will publish an update soon and also fix the stats in the original post. Indeed, Neo4j with connection pooling improved stats in a few test cases but the overall ranking is not really affected. Thanks again for helping us to improve the benchmark and creating fair conditions for all products tested!

Haha, I almost spit out my coffee when I saw how poorly we performed here! Reading the code, it's kind of incredible that Neo4j even competes - all the databases benchmarked are running with 25 concurrent database connections: https://github.com/weinberger/nosql-tests/blob/master/arango... Except Neo, which is given a single connection to work with :( https://github.com/weinberger/nosql-tests/blob/master/neo4j/... When I modify it locally to just set {maxConnectionPoolSize: 25}, like how the other databases are set up, I get roughly an order better performance. neighbors2 went from 0.0226ms to 0.0068ms, for instance. Single write sync went from 3.36415ms to 0.77549ms avg/op.. Benchmarking is hard!

One simple suggestion for one platform: https://github.com/weinberger/nosql-tests/issues/22 The more common pgtune CLI is not up to date for PostgreSQL 10+ at this time. Also there are some old, open issues that indicate the benchmarks have problems: - https://github.com/weinberger/nosql-tests/issues/16 - https://github.com/weinberger/nosql-tests/issues/13

I think the orkut dataset is already in a tab seperated format, to turn it into CSV you only need to add the column labels. http://snap.stanford.edu/data/com-Orkut.html For an example you can have a look at the import scripts: https://github.com/weinberger/nosql-tests/blob/master/arango...