Dear OrientDB community

I am loading millions of triples into an OrientDB graph using the Java
SAIL interface. With the number of loaded triples, the loading speed
seems to decrease. Since I do not know in advance the disk space
required to host all loaded triples I started loading with 200GB free
disk space.

Now the disk space left is at about 50GB and I begin to understand, that
at some point the loading process will check that there will be too
little available disk space and end the loading before all the triples
will be in the graph.

What can I do after this stop?

1) Transfer the created database to another disk / computer space and
continue loading
2) Adopt some scaling on OrientDB

Can I create a second graph instance on another computer (or another
disk), continue loading and "federate" the two OrientDB graph instances
into one in order to have on the whole one graph in two places? I am
afraid the cluster mechanism won't help me here now.

Thanks in advance
Regards

Fabio

-- 

--- 
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.

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to