Hi Ben, Sorry for delay. That is not the time of each insert. Please try to do the same in a loop of 10k times and get the average time per cycle.
However I'm working on a separate branch to speed up distributed configuration. We have good numbers so far, but we need more days to merge with 1.7.9. Lvc@ ᐧ On 21 August 2014 10:04, <[email protected]> wrote: > Dear Luca, > > I've sent you the log last Friday. I urgently need to move forward on > this. If nothing can be done to get OrientDB to work asynchronously, I have > to look at alternatives. > > OrientDB appears interesting for numerous reasons though, which is why I'd > like to stick with it. > > Regards, > - Ben > > > > > > > On Thursday, August 14, 2014 11:01:42 PM UTC+2, Lvc@ wrote: > >> Hi Ben, >> setting writeQuorum = 1 in your scenario means that the server node where >> the client is connected should be the first to respond (for obvious >> reasons), so it's crazy it takes 1 second for 1 insert. >> >> To know more try to enable logging on the server where the client is >> connected. Edit config/orientdb-server-log.properties and put these lines >> >> .level = INFO >> com.orientechnologies.level = INFO >> com.orientechnologies.orient.server.distributed.level = FINE >> com.orientechnologies.orient.server.hazelcast.level = FINE >> com.orientechnologies.orient.server.journal.level = FINE >> >> At the restart you should have much more logging information, then send >> us the log for the insert. >> >> Lvc@ >> >> >> >> On 14 August 2014 20:38, <[email protected]> wrote: >> >>> Dear colleagues, >>> >>> I am trying to figure out how to deploy a distributed orientdb setup. >>> I've followed the manuals, which explicitly state that writeQuorum 1 will >>> result in 100% asynchronous mode, however I am faced with inserts taking up >>> to 1 second or more. Example: >>> >>> orientdb {GratefulDeadConcerts}> insert into followed_by (out, in, >>> weight) values (#9:1, #9:1, 1) >>> >>> Inserted record 'followed_by#11:7061{out:#9:1,in:#9:1,weight:1} v1' in >>> 0.953000 sec(s). >>> >>> When I don't run in distributed mode, I have: >>> >>> orientdb {GratefulDeadConcerts}> insert into followed_by (out, in, >>> weight) values (#9:1, #9:1, 1) >>> >>> Inserted record 'followed_by#11:7063{out:#9:1,in:#9:1,weight:1} v1' in >>> 0.002000 sec(s). >>> >>> writeQuorum 1 has no effect, I've tried several releases from the 1.7 >>> branch and even 2.0, all with the same result. It is important to note that >>> the nodes are each located on a different continent. >>> OrientDB looks great and I would really like to use it. Any advice on >>> how to achieve asynchronous replication is greatly appreciated. >>> >>> Best regards, >>> >>> - Ben >>> >>> -- >>> >>> --- >>> 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. >>> >> >> -- > > --- > 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. > -- --- 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.
