News for hackers. Stuff that matters.
Re:Dragonfly Is Production Ready (and we raised $21M) by andrenotgiant on Tuesday March 21, 2023 @12:41PM (#35248761)
I think maybe I'm just small-potatoes, but the only limitations or constraints I've ever run into with Redis are: 1. memory utilization 2. deployment/orchestration 3. bugs I created for myself related to using caches

What are the use cases that max out Redis speed/throughput?

Re:Dragonfly Is Production Ready (and we raised $21M) by romange on Tuesday March 21, 2023 @12:50PM (#35248901)
Dragonfly is better with 1. Memory utilization (read the announcement, they mention it) 2. Deployment/orchestration - your initial threshold that forces you to scale horizontally just went up by order of magnitude. In fact for many use-cases you will never need to go horizontally with Dragonfly. 3. Dragonfly also provides a better experience when working with the system. Just a week ago one of the community contributors submitted a PR that introduces automatic recognition of the hot keys: https://github.com/dragonflydb/dragonfly/pull/951 (this feature is not ready for production use yet but we will get there). It also has a built-in open-metrics support, built in cpu-profiler support, fully asynchronous I/O that allows answering INFO commands even under load etc.
Re:Dragonfly Is Production Ready (and we raised $21M) by worldsoup on Tuesday March 21, 2023 @12:51PM (#35248926)
It really depends on the type of application but a common one is getting a large spike in traffic beyond the norm (front page on HN, flash sale, etc.) I do think #1 and #2 that you mentioned are more common constraints and are ones that also both addressed in Dragonfly (much more efficient memory utilization and ability to scale vertically which negates the need for complex orchestration)