Also if you can add amazon memory db to yor list of benchmarks, would also be interested to know more. https://aws.amazon.com/memorydb/
Is it not just Redis that AWS offers as a managed service?
Redis vs. KeyDB vs. Dragonfly vs. Skytable
41–50 of 56 posts
Re: Redis vs. KeyDB vs. Dragonfly vs. Skytable
#42Hi, I am the author of Dragonfly. Following this post, I performed the loadtest on instance m5.4xlarge, recorded myself and posted the video here: http://assets.dragonflydb.io/videos/video2609676488.mp4
the command I used to load was: "memtier_benchmark --ratio 1:0 -t 28 -c 20 -n 100000 --hide-histogram --distinct-client-seed -d 256"
I did the recording to clear out any doubts whether my benchmark results are real.
Re: Redis vs. KeyDB vs. Dragonfly vs. Skytable
#43> 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…
not if I can get equivalent (if not better) performance on my existing hardware
From your own numbers, Dragonfly get ~3.6-4 times better perf than Redis, and better than keydb (which is “just” multhreaded redis-simplifying). That indicates pretty clearly to me that we’re not getting same-or even close performance-on existing hardware; and ultimately, if performance is that important, shouldn’t we be giving our applications every advantage they can get?
Re: Redis vs. KeyDB vs. Dragonfly vs. Skytable
#44Anyone knows where can I find a good helm chart for KeyDB?
Re: Redis vs. KeyDB vs. Dragonfly vs. Skytable
#45How about including Pedis in this? It is a Redis partial reimplementation, written around Seastar: https://github.com/fastio/1store
Re: Redis vs. KeyDB vs. Dragonfly vs. Skytable
#46>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 major use-case for a KVS is *reliable, scalable* storage. RDBMS has an upper bound on scaleability. Removing the relational component removes a lot of power and flexibility, but improves performance and scalability.
That's often a good choice!
A KVS can be arbitrarily horizontally scaleable. That might not sound necessary for a small project, but even there:
1. You can deal with big data (e.g. keystroke-level event data, etc.)
2. You don't have to worry about scaleability. It's one less thing to worry about.
3. You're set up for success if you take the unicorn route.
That's not memcached. I like memcached, but it's not the same as a KVS.
Re: Redis vs. KeyDB vs. Dragonfly vs. Skytable
#47Hi, I am the author of Dragonfly. Following this post, I performed the loadtest on instance m5.4xlarge, recorded myself and posted the video here: http://assets.dragonflydb.io/videos/video2609676488.mp4 the command I used to load was: "memtier_benchmark --ratio 1:0 -t 28 -c 20 -n 100000 --hide-histogram --distinct-client-seed -d 256" I did the recording to clear out any doubts whether my benchmark results are real.
please note that I ran the bench with 30 threads with 1 connection per thread. you're not doing the same but doing 28 threads with 20 connections on each thread, effectively using 560 connections whereas I only used 30 connections. rerun the same with -t 30 and -c 1
Re: Redis vs. KeyDB vs. Dragonfly vs. Skytable
#48Hi, I am the author of Dragonfly. Following this post, I performed the loadtest on instance m5.4xlarge, recorded myself and posted the video here: http://assets.dragonflydb.io/videos/video2609676488.mp4 the command I used to load was: "memtier_benchmark --ratio 1:0 -t 28 -c 20 -n 100000 --hide-histogram --distinct-client-seed -d 256" I did the recording to clear out any doubts whether my benchmark results are real.
please note that I ran the bench with 30 threads with 1 connection per thread. you're not doing the same but doing 28 threads with 20 connections on each thread, effectively using 560 connections whereas I only used 30 connections. rerun the same with -t 30 and -c 1
I think the point he/she is trying to make is the 25x claim is real
Re: Redis vs. KeyDB vs. Dragonfly vs. Skytable
#49How about including Pedis in this? It is a Redis partial reimplementation, written around Seastar: https://github.com/fastio/1store
Because the latest commit was 3 years ago in 2019.