I've been evaluating OrientDB for use in a distributed, microservice
application to support some fairly sophisticated and connected graph
structures. In our environment, we anticipate these structures being
reasonably malleable (i.e. users will be updating and inserting vertices
and edges with some frequency) so it is not necessarily a "query-mostly"
database.
I tried just doing a bulk insert using the following configuration:
graph.getRawGraph().getLocalCache().setEnable(false);
graph.setKeepInMemoryReferences(false);
graph.getRawGraph().getTransaction().setUsingLog(false);
graph.declareIntent(new OIntentMassiveInsert());
graph.getRawGraph().declareIntent(new OIntentMassiveInsert());
both with a NoTx and Tx graph database from Java. I have to use a remote
server because I can't take the database offline to do a plocal access.
I'm seeing anywhere from 600-1500 vertices/s created and much less for
edges.
Are there some example applications for this type of usage scenario to see
how I can get better performance from the database?
For reference I'm using OrientDB 2.2.21 and the
"com.tinkerpop.blueprints.impls.orient" Java API.
Thanks
--
---
You received this message because you are subscribed to the Google Groups
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
