Live data from Hacker News

Redis vs. KeyDB vs. Dragonfly vs. Skytable

news.ycombinator.com

51–56 of 56 posts

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

#52

Earlier quoted context omitted.

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

if I'm doing my math right: redis is doing 99892 sets per sec, so 25X should be 2,497,300. the video however shows 1,023,030 which is more like 10X and NOT 25X

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

#53

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

I don't see how that matters. If it was fast then, it is still fast.

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

#54
KeyDB author here. Lack of stable kernel support was a major reason we didn't do io_uring yet. The goal for KeyDB is good performance out of the box not in specific benchmarks on specific hardware/kernel versions. As io_uring becomes mainstream we will start to support it. In 6.2.3 we have async commands which permit reads to happen outside of the global lock. In some cases it can take extra time for writes from other clients to be visible which changes the consistency model so it is off by default but dramatically improves performance when enabled.

Doing a fresh rewrite would have enabled a nicer threading model, but it would make it harder to maintain compatibility. Plus at the time it was more to suggest to Redis multithreading was both desirable and possible which were disputed back then.

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

#55

Earlier quoted context omitted.

I think the point he/she is trying to make is the 25x claim is real

if I'm doing my math right: redis is doing 99892 sets per sec, so 25X should be 2,497,300. the video however shows 1,023,030 which is more like 10X and NOT 25X

Agreed, emphasis on the word _trying_
Post reply on HN