dragonflydb /dragonfly

A modern replacement for Redis and Memcached

★ 31,875⑂ 1,294👁 169⑃ 5,948● 2,550▤ 124
C++NOASSERTIONCreated 2021-12-11www.dragonflydb.io/
Download: v2.1v2.1 ↓2.12026-11-04
+4
Daily
+34
Weekly
+94
Monthly
31,875
stars
1,294
forks
169
watchers
5,948
prs
2,550
issues
124
releases

README

Before moving on, please consider giving us a GitHub star ⭐️. Thank you!

Other languages:  简体中文 日本語 한국어 Português ภาษาไทย

Website • Docs • Quick Start • Community Slack • Dragonfly User Conference • Join the Dragonfly Community

GitHub Discussions • GitHub Issues • Contributing • AI Agents Guide • Dragonfly Cloud

 The world's most efficient in-memory data store

Dragonfly is an in-memory data store built for modern application workloads.

Fully compatible with Redis and Memcached APIs, Dragonfly requires no code changes to adopt. Compared to legacy in-memory datastores, Dragonfly delivers 25X more throughput, higher cache hit rates with lower tail latency, and can run on up to 80% fewer resources for the same-sized workload.

 Contents

- Benchmarks
- Quick start
- Configuration
- Design decisions
- Background
- Build from source
- Contributors

 Benchmarks

We first compare Dragonfly with Redis on an m5.large instance, which is commonly used to run Redis
due to its single-threaded architecture. The benchmark program runs from another
load-test instance (c5n) in the same AZ using memtier_benchmark  -c 20 --test-time 100 -t 4 -d 256 --distinct-client-seed

Dragonfly shows comparable performance:

1. SETs (--ratio 1:0):

|  Redis                                   |      DF                                |
| -----------------------------------------|----------------------------------------|
| QPS: 159K, P99.9: 1.16ms, P99: 0.82ms    | QPS:173K, P99.9: 1.26ms, P99: 0.9ms    |
|                                          |                                        |

2. GETs (--ratio 0:1):

|  Redis                                  |      DF                                |
| ----------------------------------------|----------------------------------------|
| QPS: 194K, P99.9: 0.8ms, P99: 0.65ms    | QPS: 191K, P99.9: 0.95ms, P99: 0.8ms   |

The benchmark above shows that the algorithmic layer inside DF that allows it to scale vertically
does not take a large toll when running single-threaded.

However, if we use a slightly larger instance (m5.xlarge), the gap between DF and Redis starts growing.
(memtier_benchmark  -c 20 --test-time 100 -t 6 -d 256 --distinct-client-seed):
1. SETs (--ratio 1:0):

|  Redis                                  |      DF                                |
| ----------------------------------------|----------------------------------------|
| QPS: 190K, P99.9: 2.45ms, P99: 0.97ms   |  QPS: 279K , P99.9: 1.95ms, P99: 1.48ms|

2. GETs (--ratio 0:1):

|  Redis                                  |      DF                                |
| ----------------------------------------|----------------------------------------|
| QPS: 220K, P99.9: 0.98ms , P99: 0.8ms   |  QPS: 305K, P99.9: 1.03ms, P99: 0.87ms |


Dragonfly throughput capacity continues to grow with instance size,
while single-threaded Redis is bottlenecked on CPU and reaches local maxima in terms of performance.



If we compare Dragonfly and Redis on the most network-capable

Top issues

Discussions

Latest release

v2.1 v2.1 2026-11-04
Dragonfly v2.1

This release is important because starting from this version, it changes how teams can use our software in production.
Starting from v2.1.0 the project moves from BUSL-1.1 to the Dragonfly Source-Available License (DSAL).

For more details, please read https://www.dragonflydb.io/blog/introducing-dragonfly-enterprise

Besides this much of the work is hardening. ACL enforcement is stricter, credentials are redacted from logs, and many crashes and deadlocks are fixed across blocking commands, tiered storage, Lua and search. Search gains index aliases, multi-attribute fields

Snapshot: 2026-11-16T09:23:14Z · Data license Apache-2.0 · JSON