Redis LATENCY Report Analyzer

Paste the output of redis-cli LATENCY LATEST. Before reading it, know this: the latency monitor is disabled by default, so an empty report means either no spikes or nothing recorded, and those look identical.

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 Analyze. Nothing leaves this tab.

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.

A 1.5 second command

One thread, so this is dead time for every other client

1) 1) "command"
   2) (integer) 1699000000
   3) (integer) 250
   4) (integer) 1500

Nothing recorded

The report is empty, which usually means the monitor was never switched on

(empty array)

Common mistakes

These are the ones that fail silently. The config is accepted, nothing raises an error, and the consequence arrives later.

  1. Reading an empty report as a healthy server

    The monitor is disabled by default, so an empty report is also what a server with constant stalls produces.

    Instead:CONFIG SET latency-monitor-threshold 100 first.

  2. Setting the threshold at runtime only

    CONFIG SET is lost on restart, so the monitoring quietly stops after the next one.

    Instead:Put it in redis.conf as well.

  3. Treating a fork event as something to tune

    Fork cost scales with mapped memory and is inherent to saving. There is no setting that removes it.

    Instead:Move saves to a replica, or reduce memory per instance.

  4. Using LATENCY to find which command was slow

    It names the subsystem, not the command.

    Instead:Use SLOWLOG for the specific command and its arguments.

What each latency event is actually telling you

Redis names the subsystem that stalled rather than the command that suffered, which is more useful once the names are familiar.

An empty report is ambiguous, and that is the first thing to resolve

latency-monitor-threshold defaults to 0, which means the monitor records nothing at all. An empty LATENCY LATEST is therefore consistent with a perfectly healthy server and with a server that has been stalling for months. Set the threshold before concluding anything.

fork is the cost of a background save

Redis forks for BGSAVE and for AOF rewrite, and the pause scales with how much memory the process has mapped. On virtualised hardware it is often several times worse than on bare metal. Moving saves to a replica removes it from the primary entirely.

command means an O(N) call over something large

A command event is dead time for every other client, because there is one thread. It is almost always KEYS, a full HGETALL or SMEMBERS, or a wide range query. SLOWLOG names the specific command; LATENCY only says that one was slow.

expire-cycle and eviction-cycle are capacity signals

The first means a large number of keys expired at once, which is fixed by adding jitter to TTLs so they do not land in the same second. The second means the instance is at maxmemory and doing eviction work constantly, which is a sizing problem rather than a tuning one.

What this cannot see

Only events above the threshold, only since the last LATENCY RESET, and only on this node. Latency the client experienced from network or from its own connection pool never appears here at all.

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 Persistence Config Generator How much you can afford to lose 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 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

Elsewhere on the site