Hi guys, I use OrientDB version 2.0.x. I wanted to migrate to 2.1.x (2.1.8) After running my internal tests in .NET I realized that the performance of sql UPDATE operation is really dramatic.
One of my test invokes really basic sql operation with pessimistic locking UPDATE #13:0 INCREMENT Salary = 1 LOCK RECORD in 8-12 threads. Orientdb v2.0.16 delivers nice performance on desktop machine Rate 8810,57268722467/sec, 10000 objects took 1135ms Threads=8 Rate 9033,42366757001/sec, 10000 objects took 1107ms Threads=9 Rate 8976,66068222621/sec, 10000 objects took 1114ms Threads=9 wheras v2.1.x ~ 150 ops/sec which basically kills my app. Any thoughts? Pawel PS. All ALTER/CREATE operations are sooo long now, that all my tests got 10x more time to execute. -- --- 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.
