Nothing written to disk
The right answer for a pure cache, and data loss for anything else
- durability
- none
Redis Persistence Config Generator
Choose a durability level and get the AOF and RDB settings that deliver it, with the resources they need stated rather than assumed. Both mechanisms fork, and the fork is what sizing usually misses.
persistence.conf
updates as you typeExamples
Worked setups you can load into the form above. Each one is a decision the generator makes differently, and the reason it makes it.
Every write waits for an fsync
The strongest durability, and roughly an order of magnitude slower
- durability
- strict
Common mistakes
These are the ones that fail silently. The config is accepted, nothing raises an error, and the consequence arrives later.
Sizing the machine for the dataset and not the fork
A background save forks, and copy-on-write means the extra memory is proportional to the writes during the save. On a write-heavy instance that approaches a second copy.
Instead:Size for the peak during a save.
Choosing appendfsync always for safety
It costs roughly an order of magnitude in throughput to remove a one second window that almost nobody actually needs removed.
Instead:Use everysec unless you can state why one second matters.
Turning off stop-writes-on-bgsave-error
It is usually turned off to stop an alert. It makes a failed save silent, so a full disk produces no symptom until the snapshot is needed.
Instead:Leave it on and fix the underlying failure.
Backing up by copying the AOF while it is being written
The copy can land mid-rewrite and be unusable. There is no lock to tell you this happened.
Instead:Copy the RDB, or use BGSAVE and copy the result.
AOF and RDB do different jobs, and both cost a fork
The two are usually presented as alternatives. They are better understood as a recovery mechanism and a backup mechanism, and most production instances want both.
The AOF is what you recover from
It is a log of every write, replayed on startup. With appendfsync everysec the worst case is one second of writes, which is what makes it the recovery path rather than the snapshot.
The RDB is what you copy off the box
A single compact file at a point in time. It loads much faster than replaying an AOF and it is what a backup job should take. It is a poor recovery mechanism precisely because it is point in time.
appendfsync always is not the safe default
It makes every write wait for an fsync, costing roughly an order of magnitude in throughput. It is the strongest durability Redis offers and it is rarely what was intended: everysec is the default because losing at most one second is usually the right trade.
Peak disk is not the dataset size
A rewrite writes a new AOF while the old one still exists, so peak disk is roughly the dataset plus the RDB plus two AOF copies. A full disk during a rewrite stops writes with a MISCONF error, which is a confusing symptom for a disk problem.
Rewrites are triggered by growth, not by the clock
auto-aof-rewrite-percentage 100 means rewrite when the file has doubled since the last one. The interval therefore depends entirely on the write rate, so an instance can go from one rewrite a day to one every few minutes when traffic changes.
More redis tools
Redis Hash Slot Calculator Which of the 16,384 slots does this key land in? Redis Hash Tag Tester Will these keys survive a multi-key command? Redis RESP Protocol Decoder Read what the server actually sent Redis RESP2 vs RESP3 Reply Decoder What the same reply looks like on each protocol Redis Command to RESP Exactly what your client puts on the socket Redis Glob Pattern Tester Redis globs are not shell globs Redis Connection URL Parser The path is the database number Redis Memory Unit Converter 1g and 1gb are not the same number Redis TTL Converter -1 and -2 are not durations Redis Stream ID Parser The first half is a millisecond timestamp redis.conf Validator Will Redis start with this file? Redis Production Config Linter The settings that cause incidents redis.conf to CONFIG SET Which of these can you change without a restart? Redis ACL Rule Decoder What does this user actually get? Redis ACL Validator Find the rule that does nothing Redis INFO Analyzer The numbers INFO does not print Redis SLOWLOG Analyzer What blocked everyone else Redis CLUSTER NODES Parser Read the topology, and find the gap Redis Cluster Slot Distribution Who owns how much, and what is missing Redis Keyspace Notification Flags Why your events never arrive Redis Memory Calculator The encoding decides, not the data Redis Key Count to Memory The fixed cost per key Redis Encoding Threshold Calculator One field more, several times the memory Redis Bitmap Memory Calculator Sized by the highest bit, not the set ones Redis HyperLogLog Calculator 12 KB whether you count a thousand or a billion Redis Cluster Sizing Only 60% of each node is usable Redis RDB and AOF Size Calculator The fork needs memory, not disk Redis Replication Bandwidth Calculator How long the backlog actually covers Redis Connection Pool Calculator More connections is not more throughput Redis Pipeline Calculator It removes round trips, not work Redis Cache Hit Rate Calculator 99% to 90% is ten times the backend load Redis Eviction Policy Simulator volatile- with no TTLs is noeviction Redis Cost Estimator Your rates, so nothing goes stale Redis Config File Generator A redis.conf with the reasons in it Redis ACL Generator A user that can do exactly one job Redis Maxmemory Config Generator The limit, and the headroom it needs Redis Lua Script Generator Atomic, and short enough to stay that way Redis TLS Config Generator Encrypted, and the old port actually closed Redis Sentinel Config Generator Failover that can actually be authorised Redis Cluster Config Generator Three primaries, and the bus port open Redis Docker Compose Generator Local Redis that is not on the internet Redis Client Config Generator Timeouts on both sides, and a sane pool Redis MEMORY STATS Analyzer Which number actually matters Redis Bigkeys Output Analyzer Elements are not bytes Redis CLIENT LIST Analyzer Find the connection hurting you Redis LATENCY Report Analyzer An empty report may mean nothing was recorded Redis Keyspace Prefix Analyzer Which key family is growing Redis SET Command Builder A plain SET clears the TTL Redis ZRANGE Query Builder REV reverses the argument order Redis SCAN Iteration Planner COUNT is a hint, not a page size Redis Key Name Validator Legal is not the same as workable Redis Cluster Compatibility Checker Works now, breaks when you shard