==> I'm a newbie in OrientDB :D Is there any documentation regarding transactions, performance tuning and the Java API for graphs? The closest I got were some github issues, as it is a kind of bug. Some suggested to limit the number of records within the same commit. But it seems absurd to me, because this kind of action can potentially break the ACID properties. Actually I have, lets say, 30 XML files - big but not huge - that I'm interpreting to do import to OrientDB. I could just convert them to JSON, but I do some parsing to improve the design of the data, like creating edges. I got OutOfMemory many times. First, I created an index to my natural id, which improved a lot the overall performance, but now I'm facing the outofmemory coming from commit operations. What's the proper way to delimit transactions? Another point is that I'm using the embedded mode(plocal). It's not necessary though, since I installed OrientDB in the same server. Is OrientDB really more powerful when running on server? It would be very useful to create a more complex or real world tutorial and post on the website. I could even do so if I had the knowlege. Thanks in advance!
-- --- 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.
