A write-heavy instance
Where the AOF grows quickly and rewrites are frequent
dataset: 20gb writes-per-second: 20000 bytes-per-write: 200
Give the dataset size and the write rate. The output covers RDB size, AOF growth, and the peak disk a rewrite needs, plus the memory the fork requires.
Or drop a file anywhere on this panel. Nothing is uploaded: the analysis runs in this tab.
The answer appears here
Paste on the left and press Calculate. Nothing leaves this tab.
Nothing else to flag.
No formatting problems, and nothing the rules object to. Worth remembering what that covers: this reads the file you pasted, not the account or cluster it will be applied to.
No finding matches that filter.
Real input you can load into the tool above. Each one shows a different thing going wrong, because that is what the tool is for.
Where the AOF grows quickly and rewrites are frequent
dataset: 20gb writes-per-second: 20000 bytes-per-write: 200
The same dataset with light writes, where the AOF barely grows
dataset: 20gb writes-per-second: 200 bytes-per-write: 150
These are the ones that fail silently. The config is accepted, nothing raises an error, and the consequence arrives later.
BGSAVE and AOF rewrite fork. Copy-on-write means the extra memory needed is proportional to what is WRITTEN during the save, and on a busy instance approaches a full second copy.
Instead:Size for the fork. This is the most common cause of a Redis instance being OOM killed.
A rewrite needs the old and the new AOF at the same time, plus the RDB.
Instead:Provision for the peak. A full disk during a rewrite stops writes with MISCONF.
Its default of yes makes a failed save loud. Turning it off means a full disk produces no symptom until you need the snapshot.
Instead:Leave it on, and alert on rdb_last_bgsave_status.