3 ms·

Yes, the core folks in Redis now have outlined a plan for moving towards multi-threaded awhile ago. It's honestly not made a lot of progress because raw perform

Yes, the core folks in Redis now have outlined a plan for moving towards multi-threaded awhile ago. It's honestly not made a lot of progress because raw performance matters a lot less than is argued here. As was succinctly mentioned by antirez already, Redis scales comfortably to 100s of millions of QPS with cluster mode. So, it's really building a lot of custom functionality to support better vertical scaling. Which is useful, especially when the vertical scaling keeps you on a single process. The conversation happened here, https://github.com/redis/redis/issues/8340 https://github.com/redis/redis/issues/8340, and it's not like the most pressing issue for the project. It's also not as complex as what was implemented for dragonfly, which basically has native support from the ground up for concurrent programming during command execution. It would be hard to do in C as well.

tayo42 4y ago
> raw performance matters a lot less than is argued here It matters a lot for where i work, we believe multithreading is holding redis peformance back. > Redis scales comfortably to 100s of millions of QPS with cluster mode. is there somewhere i can read more about that? curious about the server needs to do that. i worth key/value clusters a little larger then that. if possible it would be cool to use redis for it.
- reconditerose 4y ago
  > It matters a lot for where i work, we believe multithreading is holding redis peformance back. Do you run stand alone Redis or Redis cluster? Multithreading is a strategy, but it isn't the only strategy to improving raw performance. > is there somewhere i can read more about that? curious about the server needs to do that. i worth key/value clusters a little larger then that. if possible it would be cool to use redis for it. Redis scales to about ~1000 nodes with each node supporting about 200k qps, math gets you to around 200m qps as the practical upper bound for Redis these days. Multithreading would potentially help us push clusters to the billion RPS boundary.
  - romange 4y ago
    Do you actually have a customer that runs a cluster of 1000 nodes? No need to answer this question. I can guess the answer.
- romange 4y ago
  @tayo42 - we would love to engage and see how Dragonfly can fit the use-cases of your company.
  - tayo42 4y ago
    Hey sure don't mind chatting. How should I reach out?
    - romange 4y ago
      @tayo42 roman@dragonflydb.io

tayo42 4y ago

> raw performance matters a lot less than is argued here It matters a lot for where i work, we believe multithreading is holding redis peformance back. > Redis scales comfortably to 100s of millions of QPS with cluster mode. is there somewhere i can read more about that? curious about the server needs to do that. i worth key/value clusters a little larger then that. if possible it would be cool to use redis for it.

reconditerose 4y ago
> It matters a lot for where i work, we believe multithreading is holding redis peformance back. Do you run stand alone Redis or Redis cluster? Multithreading is a strategy, but it isn't the only strategy to improving raw performance. > is there somewhere i can read more about that? curious about the server needs to do that. i worth key/value clusters a little larger then that. if possible it would be cool to use redis for it. Redis scales to about ~1000 nodes with each node supporting about 200k qps, math gets you to around 200m qps as the practical upper bound for Redis these days. Multithreading would potentially help us push clusters to the billion RPS boundary.
- romange 4y ago
  Do you actually have a customer that runs a cluster of 1000 nodes? No need to answer this question. I can guess the answer.
romange 4y ago
@tayo42 - we would love to engage and see how Dragonfly can fit the use-cases of your company.
- tayo42 4y ago
  Hey sure don't mind chatting. How should I reach out?
  - romange 4y ago
    @tayo42 roman@dragonflydb.io