in particular as Arango did use the 2.2 alpha with so called performance improvements.
The good thing is, that the OrientDB is not trying the same that VW did when they discovered that their engines where badly constructed. But Shortest Path: Arango 61 ms, Orientdb 35 sec, this is truly unacceptable. As well as 464 ms for a neighbour-search in Arango compared with 2,4 sec. in OrientDB. Instead of improving the Database by adding fancy new features, maybe its best to stabilize the Project and work on a reliable Production-Release. -- --- 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.
