Live data from Hacker News

“The benchmark numbers are completely wrong for both databases”

github.com

51–58 of 58 posts

Re: “The benchmark numbers are completely wrong for both databases”

#51

Well, the author cares enough about RethinkDB to test it, even if he's a mongodb fan, even if his first benchmark was wrong, he was right to publish it: you all helped him when you pinpointed the problems in his tests... Thanks you for that. I don't see any marketing here, just the "do your own benchmark" best practice, and the "share with community" best practice... Does it make it a perfect benchmark? No, but at le…

So basically you're saying that because he cares and because he tried, and because the comments were dumb, nobody should criticize him? Do you really not care about getting accurate results? Running benchmarks is an engineering practice. If you failed to get meaningful results, you failed. Yes, he cares, yes, he tried, yes, the comments are dumb, but he still failed. Sure, I'll give the guy kudos for trying, but I'm…

> So basically you're saying that because he cares and because he tried, and because the comments were dumb, nobody should criticize him?

I don't think anybody is saying that.

Re: “The benchmark numbers are completely wrong for both databases”

#52
post #30

Well, the author cares enough about RethinkDB to test it, even if he's a mongodb fan, even if his first benchmark was wrong, he was right to publish it: you all helped him when you pinpointed the problems in his tests... Thanks you for that. I don't see any marketing here, just the "do your own benchmark" best practice, and the "share with community" best practice... Does it make it a perfect benchmark? No, but at le…

> the author has corrected the discrepancies since then As of the time I posted this comment, the blog post still seems to be comparing indexed MongoDB operations against non-indexed RethinkDB operations. Under those conditions I'd expect RethinkDB to be at least 1000x slower than MongoDB. The fact that he's finding that RethinkDB is only 3x slower than MongoDB makes me think that there are still other major problems…

> Maybe we need to start a "best practice" of checking in with the maintainers of a project before publishing benchmark results about the project.

http://en.wikipedia.org/wiki/David_DeWitt

Re: “The benchmark numbers are completely wrong for both databases”

#53
post #30

Earlier quoted context omitted.

> the author has corrected the discrepancies since then As of the time I posted this comment, the blog post still seems to be comparing indexed MongoDB operations against non-indexed RethinkDB operations. Under those conditions I'd expect RethinkDB to be at least 1000x slower than MongoDB. The fact that he's finding that RethinkDB is only 3x slower than MongoDB makes me think that there are still other major problems…

Some mistakes in his benchmarks, among probably others: - I don't see any mongodb index creation, so mongodb is inserting with no index while rethinkdb is inserting with the index. That's probably why there's a gap between the two - there's no mongodb index, and rethinkdb queries do not make use of the index (this is probably why rethinkdb is not 1000x slower: both aren't using indexes) - the $in query should be last…

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...

Re: “The benchmark numbers are completely wrong for both databases”

#54
post #53

Earlier quoted context omitted.

Some mistakes in his benchmarks, among probably others: - I don't see any mongodb index creation, so mongodb is inserting with no index while rethinkdb is inserting with the index. That's probably why there's a gap between the two - there's no mongodb index, and rethinkdb queries do not make use of the index (this is probably why rethinkdb is not 1000x slower: both aren't using indexes) - the $in query should be last…

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...

Yes, 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.

Re: “The benchmark numbers are completely wrong for both databases”

#55
post #48

Earlier quoted context omitted.

So basically you're saying that because he cares and because he tried, and because the comments were dumb, nobody should criticize him? Do you really not care about getting accurate results? Running benchmarks is an engineering practice. If you failed to get meaningful results, you failed. Yes, he cares, yes, he tried, yes, the comments are dumb, but he still failed. Sure, I'll give the guy kudos for trying, but I'm…

You must be fun at parties...

I am, because I'm there to have fun. Looking at DB benchmarks can be fun, but there are other reasons I do it.

Re: “The benchmark numbers are completely wrong for both databases”

#56
post #51

Earlier quoted context omitted.

So basically you're saying that because he cares and because he tried, and because the comments were dumb, nobody should criticize him? Do you really not care about getting accurate results? Running benchmarks is an engineering practice. If you failed to get meaningful results, you failed. Yes, he cares, yes, he tried, yes, the comments are dumb, but he still failed. Sure, I'll give the guy kudos for trying, but I'm…

> So basically you're saying that because he cares and because he tried, and because the comments were dumb, nobody should criticize him? I don't think anybody is saying that.

Please, enlighten me on what you think weddpros is saying.

Re: “The benchmark numbers are completely wrong for both databases”

#57
post #30

Earlier quoted context omitted.

> the author has corrected the discrepancies since then As of the time I posted this comment, the blog post still seems to be comparing indexed MongoDB operations against non-indexed RethinkDB operations. Under those conditions I'd expect RethinkDB to be at least 1000x slower than MongoDB. The fact that he's finding that RethinkDB is only 3x slower than MongoDB makes me think that there are still other major problems…

Not sure why you are frustrated it's just a blog post by someone who was inexperienced with your product. At least he owned up to the mistakes and was willing to fix it. It's an opportunity for you to work with the guy to show him how to do it properly and write a blog post of your own. I would say that you probably should look at your API because I've never used a database that required me to explicitly define which…

GP is frustrated because it's not just the one blog post. Even if the author is willing to correct it, the original bad data will tend to get more exposure, because most people won't check in for corrections (unless they see a post like OP). Then, there'll be another crappy benchmark next month or next week. If I thought my product was being judged this way, it would drive me frothing mad.

Re: “The benchmark numbers are completely wrong for both databases”

#58
post #51

Earlier quoted context omitted.

> So basically you're saying that because he cares and because he tried, and because the comments were dumb, nobody should criticize him? I don't think anybody is saying that.

Please, enlighten me on what you think weddpros is saying.

Weddpros was making the point that criticism worked. The poster tried (An important first step), failed, and critical people pointed out his errors. Weddpros points out the poster corrected those errors because he received criticism. Weddpros is clearly a fan of critical feedback.
Post reply on HN