Performance reality

[StarpTech]

From the last successfully build on travis:

  Bug #27: Slow compared to Restful API
Binary Protocol Took  1587ms, 3151 documents per second
  ✓ should load a lot of records quickly, using the binary raw command interface (1588ms)
Rest Protocol Took  1689ms, 2960 documents per second
  ✓ should load a lot of records quickly, using the rest raw command interface (1690ms)
Binary DB Api Took  643ms, 7776 documents per second
  ✓ should load a lot of records quickly (644ms)
Binary Record Load Took  1928ms, 2593 documents per second
  ✓ should load a lot of records, one at a time, using binary (1928ms)
    - should load a lot of records, one at a time, using rest

Following questions:

1. Why is REST almost same performant as Binary?
2. Why is orientjs so slow in general? 8000docs/s ?!

OrientDB is incredibly fast (storing 220,000 records per second on common hardware).

OTE: Release v2.2 contains big improvement on marshalling by using native C driver.

We not even reach a quarter and this is the new 2.2.2 release + native record seralization. What happens here ? Did you benchmark on a raspberry pi?

btw: Its also good to note that only the 2.2.x series can use the native marshaling.

[wolf4ood]

@StarpTech

that is not really a benchmark, it's just a small comparison between the 2 protocols. Btw if you see the single record load for multiple times, there is much difference between the 2 protocols, meanwhile on the single spot request the values are almost equals.

It's running on travis so i think it is not such performant environment.

[StarpTech]

Hi @maggiolo00 thanks. I recommend to create a meaningful benchmark to prove the performance boost with OrientJs 2.2 and Orientdb 2.2.