Thanks for the response. So then, the only tcp-ip calls would be for the replication. And if I want to write to more masters, I have to start the same java app on each of the different master machines I want to be writing to, with the same configuration file (hazelcast.xml) ?
On Monday, January 5, 2015 2:28:31 PM UTC+2, Lvc@ wrote: > > Hi Andrei, > Java API is the fastest solution, specially because you could embed > OrientDB in the same JVM of your app avoiding the entire TCP/IP call. > > Lvc@ > > > On 5 January 2015 at 12:25, Andrei Stoiculescu <[email protected] > <javascript:>> wrote: > >> Batching is very important too. Was wondering whether this is possible >> from the server side functions. >> >> >> On Monday, January 5, 2015 12:24:58 PM UTC+2, Andrei Stoiculescu wrote: >>> >>> Hi, >>> >>> I am looking to setting up an OrientDb application, in which we will be >>> doing a lot of inserts per second (hundreds to thousands). >>> So, performance is really important. >>> >>> I was wondering, which is faster : >>> 1 Javascript or Sql functions running on the server, or >>> 2 Java api running on a local storage system. Same machine with one >>> master. >>> >>> In our architecture the master-master replication is really important. >>> So we will have more masters. >>> But only one java app, will single threaded-ly write to OrientDb. >>> >>> Thanks and Regards, >>> Andrei >>> >>> -- >> >> --- >> 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] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > > -- --- 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.
