dragonflydb /dragonfly
A modern replacement for Redis and Memcached
★ 31,875⑂ 1,294👁 169⑃ 5,948● 2,550▤ 124
+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
#5662test_replicaof_reject_on_load59 comments · 2025-08-12#5625Snapshot causes dragonfly fresszing?42 comments · 2025-08-06#3170Software error on replication36 comments · 2024-06-12#2824FR: Allow setting amount of snapshots (logrotate for snapshots)16 comments · 2024-04-02#8226Rapid increase in psync_buffer_bytes causing high memory usage12 comments · 2026-09-03#7652Design: Memory efficient OAH Entry Encoding for OAHSet12 comments · 2026-06-19#3000Repositories for Linux distributions install12 comments · 2024-05-02#303Are there support memcached binary protocols?12 comments · 2022-09-16
Discussions
#8793New license 100 vCPU limit1 comments · 2026-11-11#8744v2.10 comments · 2026-11-04#8331v2.0.00 comments · 2026-09-16#8261Issue: HINCRBY commands taking 10–30 ms despite low memory usage2 comments · 2026-09-08#8166Support skipping TLS certificate/hostname verification for S3 snapshot storage (private CA / self-signed endpoints)0 comments · 2026-08-25#7990v1.40.01 comments · 2026-08-04#7693docker.dragonflydb.io - docker pull failure1 comments · 2026-06-24#7549v1.39.00 comments · 2026-06-09
Latest release
v2.1 v2.1 2026-11-04Dragonfly 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