![]() Additionally, we benchmarked ArangoDB against a multi-model database, OrientDB. For instance, this time we included the JSONB format for PostgreSQL.įor comparison, we used three leading single-model database systems: Neo4j for graph MongoDB for document and PostgreSQL for relational database. We incorporated much of that feedback in this benchmark. Great teamwork, crew!Īfter we published the previous benchmark, we received plenty of feedback from the community - thanks so much to everyone for their help, comments and ideas. Deep thanks to my teammates Mark, Michael and Jan for their excellent and tireless work on this benchmark. Also big thanks to Spain and ToroDB CEO/Founder Alvaro Hernandez for contributing your knowledge for PostgreSQL. Thanks Hans-Peter for your help! Big thanks as well to Max De Marzi and “JakeWins” both team Neo4j for their contributions and improvements to the 2018 Edition of our benchmark. ![]() Wrapping my head around the JSON notation is for sure not impossible but boy can querying data be complicated. Besides all of these factors, machines are now faster, so a new benchmark made sense.īefore I get into the benchmark specifics and results, I want to send a special thanks to Hans-Peter Grahsl for his fantastic help with MongoDB queries. So we waited until its integration was finished before conducting a new benchmark test. Plus, there are some major changes to ArangoDB software.įor instance, in latest versions of ArangoDB, an additional storage engine based on Facebook’s RocksDB has been included. Since the previous post, there are new versions of competing software on which to benchmark. This article is part of ArangoDB’s open-source performance benchmark series. Introduction to the Benchmark and Acknowledgements
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |