OrientDB 2.2 Released – Open-Source Graph Database(orientdb.com)
orientdb.com
OrientDB 2.2 Released – Open-Source Graph Database
http://orientdb.com/released-orientdb-v2-2/
4 comments
I had the same problem with a fairly 50/50 read/update database, about 20M reads/20M updates a day. Brought it to it's knees. Postgres handled it no problem.
I work with graphs all the time and I've never had any luck with any graph database. Graph databases seem to flagrantly waste resources, especially when importing data.
That said, I should find out if OrientDB's announced "tenfold" performance increase is enough.
That said, I should find out if OrientDB's announced "tenfold" performance increase is enough.
If you could use mysql as a replacement doesn't that mean you didn't need a graph database to start with though?
[deleted]
worth reading: http://orientdbleaks.blogspot.com.ar/2015/06/the-orientdb-is...
I've had several issues with the "distributed" setup among others.
I've had several issues with the "distributed" setup among others.
Was thinking of using neo4j for an upcoming project. Did anyone benchmark OrientDB against Neo4j
A 3rd GraphDB vendor, ArangoDB, did benchmark both of them. You can find the results on their blog at https://www.arangodb.com/2015/10/benchmark-postgresql-mongod...
Definitely, worth checking out! Much stable and fast.
I tried to use it with a 80,000,000 product database with about 60,000,000 updates a day (edges between sellers and products labeled by price) and it was unusable with the same sizing as a mySQL database that handled it easily.
It seemed great though. Especially since neo4j open source is quite restrictive (clustering is a commercial only feature not available in the OSS version).