Has anyone had any luck with Orient and large database?
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).
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.
9 comments
[ 3.2 ms ] story [ 24.1 ms ] threadI 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).
That said, I should find out if OrientDB's announced "tenfold" performance increase is enough.
I've had several issues with the "distributed" setup among others.