Hello, First things first, Thank you very much for your answer, your help is much appreciated.
l.garulli 1. We are using a remote connection 2. We run a standalone OrientDB server on an isolated vm, it runs with 8GB of RAM, no problems going from this side 3. To insert data we rely only on the regular Graph API, using indeed vertices and edges. We thought of the possibility of writing a big file composed by SQL statement to insert the data but didn't had the time to do so lately. 4. We do use transactions, i understand that i may be costly in RAM but this much ? Anyway, we are in a prototype environment i won't break anything so i will try to patch our generator to make it work without transactions. Oleksandr Gubchenko I don't get exactly what you are proposing, maybe i did not made myself clear enough about this. The memory issue we are experiencing is at the generator (which you can see as our client), the OrientDB server is running just fine. Still i will try to make something out of those commands, I'm curious. Thanks again, i will give you updates -- --- 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.
