3 ms·
In the benchmark script [1] that the author provided on his GitHub account, there's a call to ensure_index() for MongoDB. And he's reporting an average latency
by timmaxw 11y ago
In the benchmark script [1] that the author provided on his GitHub account, there's a call to ensure_index() for MongoDB. And he's reporting an average latency of 0.15ms for MongoDB read operations, so it's pretty clear that the MongoDB index is actually being used.
[1] https://github.com/martinrusev/rethinkvsmongo-benchmark/blob/master/benchmark.py https://github.com/martinrusev/rethinkvsmongo-benchmark/blob...
- weddpros 11y agoYes, this kind of latency definitely says "indexed". When I wrote this, I'd read a rethinkDB employee say "it's not using the index on rethinkdb", and performance was similar (3x) between the two. I trusted the "no index" path, and couldn't find an ensureIndex command... So I assumed there was no index on mongodb. Truth is, this kind of performance can only come with indexes, on RethinkDB and mongodb.