Hi Alexander, We're close to release final 2.0 where we improved synchronous replication of 3x and now we have a new asynchronous replication able to replicate thousands of records per seconds (depends by hw/sw/network cfg).
Your quote about 150k/sec was referring to 1 node only, and we updated that value to 220k/sec now. About Aerospike, what persistence engine did you use? Lvc@ On 2 December 2014 at 09:03, Alexander Sahler <[email protected]> wrote: > Hello everybody. > > I'm evaluating OrientDB (1.7.9 as 2.0-M3 is unstable) in a two-node > cluster environment. Both machines are 4 core, 4GB RAM in a local (1GBit) > network. > When running on one node, I manage to place about ~400/s simple objects in > the database. As soon as I start the second node, insert rate drops down to > 80~90 per second. > > A test with Aerospike (replicated) gave about 10000 puts/s on the same > machines with the same client. Only persistence layer did change. > > On your page you write about OrientDB to be able to put 150.000 > transactions per second on "commodity hardware". How to achieve this rates? > > Best regards, > > Alexander. > > -- > > --- > 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.
