The Definitive In-Memory Data Store Benchmark Report
As engineering teams face increasing pressure to deliver sub-millisecond performance at scale, choosing the right in-memory data store is no longer a minor infrastructure decision. This benchmark report provides a rigorous, side-by-side analysis of Dragonfly, Redis, and Valkey across throughput, latency, memory efficiency, and scalability tested across AWS and Google Cloud environments under real-world, high-concurrency conditions.
Inside this report, you'll find:
- How Dragonfly achieves 25x the throughput of Redis on identical hardware
- Why Valkey's single-threaded bottleneck limits scaling, and how Dragonfly delivers 2.4x to 4.6x higher throughput as core counts grow
- How Dragonfly's memory efficiency reduces storage requirements by up to 45% versus Valkey for sorted set workloads
- Why Dragonfly's multi-threaded, shared-nothing architecture unlocks 61% more throughput when moving to newer cloud hardware, with no retuning required
- The hidden operational costs of Redis snapshotting and how Dragonfly eliminates dangerous memory spikes entirely
Whether you're evaluating a migration from Redis, weighing Valkey as an alternative, or looking to right-size your infrastructure spend, this report gives you the data to make a confident decision.
Trusted by the best
Featured In-memory Data Resources
One Dragonfly Instance, Ten Workloads: How ACL Database Selectors Work
Learn how Dragonfly's ACL database selectors let you run multiple isolated workloads on a single instance — without spinning up separate Redis instances per app.

Memory-Aware Rebalancing Is Now Automatic in Dragonfly Cloud
Most cluster rebalancing tools spread hash slots evenly by count, not by memory — which does nothing for a shard overloaded with large values. Dragonfly Cloud's shard memory balancing tracks utilization at the individual slot level and automatically redistributes slot...
No Sentinels Required: How Dragonfly Cloud Cuts Failover to One Second
Dragonfly Cloud cuts Redis failover from 30+ seconds to 1 second by embedding failure detection directly into the data plane. No Sentinel required.
