A hash under the threshold
Twenty fields per key, which stays in the compact encoding
type: hash keys: 1000000 fields: 20 field-bytes: 12 value-bytes: 32
Redis Memory Calculator
Describe the keys and get a memory range, with the encoding that decides it named. Every figure is a range, because the exact number depends on allocator behaviour and on data this cannot see.
Paste below, or drop a file anywhere on this panel
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.
Formatted
Results
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.
Wanted a different tool?
- Redis Key Count to Memory if all you have is a key count and an average size, because that reports how much of the total is per-key overhead rather than data.
- Redis Encoding Threshold Calculator if you want the exact threshold where an encoding flips, because that is the cliff this calculator's range is wide because of.
Examples
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.
Past the threshold
The same keys with 200 fields, which switches to a hashtable
type: hash keys: 1000000 fields: 200 field-bytes: 12 value-bytes: 32
Common mistakes
These are the ones that fail silently. The config is accepted, nothing raises an error, and the consequence arrives later.
Sizing from the data alone
Key names, the dict entry, the robj and allocator rounding are frequently more than the values, and none of it appears in a back-of-envelope calculation.
Instead:Include the per-key overhead. For small values it dominates.
Treating the estimate as a measurement
Fragmentation, copy-on-write during a save and client buffers all sit outside this model.
Instead:Load a sample and read used_memory. MEMORY USAGE on a real key is the ground truth.
Ignoring the version
7.0 replaced ziplist with listpack and 7.2 added listpack for sets. The same data occupies different amounts on different versions.
Instead:Set the version. It changes the encoding and therefore the answer.
Further reading
The problem this tool checks for, written up in full.
Related redis tools
Redis Key Count to Memory The fixed cost per key 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 Keyspace Notification Flags Why your events never arrive Redis Keyspace Prefix Analyzer Which key family is growing Redis Memory Unit Converter 1g and 1gb are not the same number
All 53 redis tools