It is interesting that the OrientDB results came up with worse results on reads than Arango did.
I also agree with Dario, that the second report results from Arango should have been used in the result values. It seems they are trying to be fair. The same should be returned. You refer to them reworking the benchmarks, yet by including the incredibly bad results of their first test and not the second set of results, you are sort of committing the same marketing whitewash you accuse them of doing. Not really a noble gesture. I'm also interested in what was done, in laymen's terms, to improve the neighbors performance. Also, when you think you will be returning with the improved NodeJS driver for hopefully improved read performance results? Those are the only ones where I am now raising an eyebrow. And how hard would it be to get this benchmark done with some other languages? Like Java, PHP and Python? Not saying, you gents should do them, just wondering what you think the amount of work it would be. A couple hours, couple days, couple weeks? And at any rate, thanks for the efforts made in this. In the end, everyone wins, if the knife throwing can be avoided. Scott -- --- 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.
