Replies: 2 comments
-
Hi @re-thc
From my understanding Valkey does not exactly support parallel processing. The commands you are running are still There is also the memory side. Df does not use Redis Dictionary to store key/values but rather something called a DashTable which effectively has less metadata waste (meaning that an entry in the dash table requires less bytes than the redis dictionary). Furthermore, our shared nothing architecture allows parallel execution due and our transaction framework does not require complicate locking strategies alleviating a lot of the bottlenecks associated with the traditional lock managers found in shared memory systems. All in all my two cents are -- and without any actual benchmarks-- I would expect DF would offer way better performance and memory characteristics. |
Beta Was this translation helpful? Give feedback.
-
Less words, more deeds. Will you do a benchmark comparison? There are already independent benchmarks of Valkey on many third-party sites, and it shows excellent results, not inferior to yours. Considering that Valkey supports all Redis commands and, most importantly, can scale horizontally in a cluster deployment (supported out of the box), I wonder how dragonfly will look against it. |
Beta Was this translation helpful? Give feedback.
-
Hi, most of the benchmarks are against Redis. Valkey now supports parallel processing and other features.
How does Dragonfly compare?
Beta Was this translation helpful? Give feedback.
All reactions