Mongo Vs Redis, The Increment Battle
devdazed.com
Mongo Vs Redis, The Increment Battle
1–10 of 27 posts
Re: Mongo Vs Redis, The Increment Battle
#2I've no clue about MongoDB performances, and which of Redis and MongoDB is faster incrementing integers, but for sure this benchmark is completely useless, as it is actually measuring a mix of client library latency and round trip time, being it single threaded, making no assumptions about the durability requirements, and so forth.
For sure it seems like that MongoDB client library you are using has a smaller latency, perhaps it is a C library? As Redis-rb is instead written in Ruby itself.
Another huge problem of this benchmark is that it should try to increment a random key per every iteration, out of a dataset with a few millions of keys, as this is realistically what you need. You'll see how Redis with 50 clients will increment this counters 100k times per second or more without any performance degradation as the number of keys grows.
Re: Mongo Vs Redis, The Increment Battle
#3You could make electricity from the amount of eyerolling this article is going to generate here on HN.
Re: Mongo Vs Redis, The Increment Battle
#4I've no clue about MongoDB performances, and which of Redis and MongoDB is faster incrementing integers, but for sure this benchmark is completely useless, as it is actually measuring a mix of client library latency and round trip time, being it single threaded, making no assumptions about the durability requirements, and so forth. For sure it seems like that MongoDB client library you are using has a smaller latency…
I wouldn't say it's completely useless as it shows that Mongo is faster in a single threaded process, using the most popular ruby client of each system.
If I were writing a high-concurrency multi-threaded system to handle millions of keys at a time, Ruby would not be my first choice by far.
Re: Mongo Vs Redis, The Increment Battle
#5More accurate title:
(Mongo + Mongo Ruby Gem) Vs (Redis + Redis Ruby Gem), The Increment Battle with No Useful Statistical Analysis Included
Re: Mongo Vs Redis, The Increment Battle
#6I've no clue about MongoDB performances, and which of Redis and MongoDB is faster incrementing integers, but for sure this benchmark is completely useless, as it is actually measuring a mix of client library latency and round trip time, being it single threaded, making no assumptions about the durability requirements, and so forth. For sure it seems like that MongoDB client library you are using has a smaller latency…
I wouldn't say it's completely useless as it shows that Mongo is faster in a single threaded process, using the most popular ruby client of each system. If I were writing a high-concurrency multi-threaded system to handle millions of keys at a time, Ruby would not be my first choice by far.
I have to agree with antirez here and call shenanigans. "WOW, MongoDB is almost a full 40% faster at incrementing than Redis" is simply a false statement. The correct conclusion for your post is "WOW, incrementing the same key 100k times with the mongo ruby gem in a very specific, single-threaded ruby application is 40% faster than incrementing one key 100k times with the redis ruby gem the in that same ruby application." If anyone makes a decision about a real world application based on your post, they will be making a huge mistake.
Re: Mongo Vs Redis, The Increment Battle
#7I've no clue about MongoDB performances, and which of Redis and MongoDB is faster incrementing integers, but for sure this benchmark is completely useless, as it is actually measuring a mix of client library latency and round trip time, being it single threaded, making no assumptions about the durability requirements, and so forth. For sure it seems like that MongoDB client library you are using has a smaller latency…
I wouldn't say it's completely useless as it shows that Mongo is faster in a single threaded process, using the most popular ruby client of each system. If I were writing a high-concurrency multi-threaded system to handle millions of keys at a time, Ruby would not be my first choice by far.
> it shows that Mongo is faster in a single threaded process, using the most popular ruby client of each system.
No, it doesn't. You ran 100k increments on one key and divided by time ONCE and printed the result.
Plus this was on your Macbook Pro, which is probably running a mail client, Twitter client, web browser, and hundreds of other things that could have affected the times.
Graphing the response times for each increment would be a good way to start looking at what the data really shows, instead of going by a single opaque, fairly useless number.
Re: Mongo Vs Redis, The Increment Battle
#8Can you give the mongo and reddis version numbers?
Just curious if you were using reddis 2.0 or possibly 2.2 ? Also what version of the reddis client were you using? There were some performance improvements recently.
Edit: thanks for sharing your experience, even if your test wasn't done with the help of a nobel winning computer team, it can still be useful data.
Re: Mongo Vs Redis, The Increment Battle
#9I've no clue about MongoDB performances, and which of Redis and MongoDB is faster incrementing integers, but for sure this benchmark is completely useless, as it is actually measuring a mix of client library latency and round trip time, being it single threaded, making no assumptions about the durability requirements, and so forth. For sure it seems like that MongoDB client library you are using has a smaller latency…
I wouldn't say it's completely useless as it shows that Mongo is faster in a single threaded process, using the most popular ruby client of each system. If I were writing a high-concurrency multi-threaded system to handle millions of keys at a time, Ruby would not be my first choice by far.
Ok, I agree with antriz's statement. My results are very specific. I will make note and be sure to be very thorough next time around.
Re: Mongo Vs Redis, The Increment Battle
#10Can you give the mongo and reddis version numbers? Just curious if you were using reddis 2.0 or possibly 2.2 ? Also what version of the reddis client were you using? There were some performance improvements recently. Edit: thanks for sharing your experience, even if your test wasn't done with the help of a nobel winning computer team, it can still be useful data.
I was using redis 2.0 and mongo 1.6.5 with the latest drivers for each.