Live data from Hacker News

Redis vs. KeyDB vs. Dragonfly vs. Skytable

news.ycombinator.com

21–30 of 56 posts

Re: Redis vs. KeyDB vs. Dragonfly vs. Skytable

#21
> I was NOT able to reproduce the 25X speed that Dragonfly claims

The Dragonfly benchmark which showed 25x faster was run on c6gn.16xlarge which has 64 vCPU. The m5.4xlarge you used "only" has 16 vCPU. Since Dragonfly is achieving its performance by using multiple threads it's not weird that you weren't able to replicate its performance gain.

In my opinion, when it comes to these types of multi-threaded benchmarks it's much better to separate the "baseline, one-process performance" from "how it scales with number of processes". E.g. if you first pin Dragonfly to only run on a single core you can find the baseline performance compared to Redis, and then you can run different benchmarks of Dragonfly with increasing number of cores to see how it scales. This should give you much better understanding of how the system behaves. (The release of Dragonfly actually prompted me to write a blog post on this: https://t.holmium.no/dia/apples-vs-oranges/)

Re: Redis vs. KeyDB vs. Dragonfly vs. Skytable

#22
This article interests me as it has been a bucket list todo to get a good sense of some of the key/value offerings, thank you for posting them.

Quick ask: I don’t see “some” of the other offering out there like MemCached… what was the criteria used to select these? I don’t see any source of how the test where run, specs of the systems, how the DB where set up, etc. Would be very valuable to have in order to attempt to re-validate these test on our own platform. I also came back and saw some of your updates to the outcomes, While the Get/SET numbers are provided, I don’t find a reference to time, resource utilization, or time which would IMO make the data more valuable in understating how the numbers where achieved. * I might be a factor of the benchmarks themselves, but would add value IMO to your fantastic post.

Re: Redis vs. KeyDB vs. Dragonfly vs. Skytable

#24
post #13

>Redis, which I'd like to call the "original" key/value store My old friend Memcached just came by and want to say Hello. He is still alive and kicking. Netflix has been treating him well.

> My old friend Memcached just came by and want to say Hello. He is still alive and kicking. Netflix has been treating him well. Forgot my dear buddy. Added it back.

BerkeleyDB's been around since the mid-90s…

Re: Redis vs. KeyDB vs. Dragonfly vs. Skytable

#25
> Dragonfly expects you to have the latest hardware[6] and the latest kernel[7] on all your servers. I find this outrageous because not all servers run 5.10

I don’t understand why this is “outrageous”? There’s performance features and better hardware utilisation in newer kernels? If you want the performance offered by the applications built on top of these, then arguably you should be prepared to run the hardware and software required to achieve this.

Re: Redis vs. KeyDB vs. Dragonfly vs. Skytable

#27
post #14
post #13

>Redis, which I'd like to call the "original" key/value store My old friend Memcached just came by and want to say Hello. He is still alive and kicking. Netflix has been treating him well.

Wow! I was under the very wrong impression that memcached hadn't been updated in a long time. It has been having regular releases for longer than I thought. Great to hear!

Somewhere along the ling, lots of ( well deserved ) hype went to Redis and Postgres, and people thought Memcached and MySQL died.

I have been wondering for a long time if we will ever see Memcached 2.0 and MySQL 9.0

Re: Redis vs. KeyDB vs. Dragonfly vs. Skytable

#28
post #13

>Redis, which I'd like to call the "original" key/value store My old friend Memcached just came by and want to say Hello. He is still alive and kicking. Netflix has been treating him well.

There is a 100% binary protocol compatible implementation in Rust.

https://memc.rs/intro

Re: Redis vs. KeyDB vs. Dragonfly vs. Skytable

#29
post #19

Redis and sqlite are two projects I can't really believe exist. They both are absolutely magical.

Could you explain why?

Both are small projects by small teams (though I don't know how small Redis team is now). They have insane performance characteristics with rather small footprints and a wealth of functionality.

Re: Redis vs. KeyDB vs. Dragonfly vs. Skytable

#30
post #13

>Redis, which I'd like to call the "original" key/value store My old friend Memcached just came by and want to say Hello. He is still alive and kicking. Netflix has been treating him well.

Memcached isn't even a "key/value" store (in database terms), it's a cache.

https://github.com/memcached/memcached/wiki/ProgrammingFAQ#w...

Post reply on HN