LATENCY-GRAPH(3valkey)

📦
version 9.0.6 · 2 versions
, in fedora 44

💅 LATENCY-GRAPH (from the 3valkey manual, aka the Valkey Command Manual bestie) ✨

🌸 NAME

latency-graph — bestie, it returns a latency graph for an event. that's it. that's the whole job. 🎀

🦋 SYNOPSIS

LATENCY GRAPH event

✨ DESCRIPTION

So it produces an ASCII-art style graph for the event you named. yes, literally art. in your terminal. 💖

LATENCY GRAPH lets you intuitively understand the latency trend of an event via state-of-the-art visualization. like, the vibes of your latency over time, rendered. it's giving "main character data scientist". it can be used for quickly grasping the situation before resorting to means such parsing the raw data from valkey-latency-history(7) LATENCY HISTORY or external tooling. so basically: peek at the graph first, do the whole forensic deep-dive later. 🙈

Valid values for event are:

  • active-defrag-cycle
  • aof-fsync-always
  • aof-stat
  • aof-rewrite-diff-write
  • aof-rename
  • aof-write
  • aof-write-active-child
  • aof-write-alone
  • aof-write-pending-fsync
  • command
  • expire-cycle
  • eviction-cycle
  • eviction-del
  • fast-command
  • fork
  • rdb-unlink-temp-file
no cap, those are the ONLY ones. don't go inventing your own event name, it's not gonna slay. 🫶

💌 REPLY

valkey-protocol(7) Bulk string reply: Latency graph

🔥 COMPLEXITY

O(1)

constant time. iconic. no thoughts, head empty, fast as hell. 💅

👑 ACL CATEGORIES

@admin @dangerous @slow

🌈 HISTORY

  • Available since: 2.8.13

🍓 EXAMPLES

127.0.0.1:6379> latency reset command
(integer) 0
127.0.0.1:6379> debug sleep .1
OK
127.0.0.1:6379> debug sleep .2
OK
127.0.0.1:6379> debug sleep .3
OK
127.0.0.1:6379> debug sleep .5
OK
127.0.0.1:6379> debug sleep .4
OK
127.0.0.1:6379> latency graph command
## command - high 500 ms, low 101 ms (all time high 500 ms)

   #_
  _||
 _|||
_||||

11186
542ss
sss

The vertical labels under each graph column represent the amount of seconds, minutes, hours or days ago the event happened. For example “15s” means that the first graphed event happened 15 seconds ago. 🕰️

The graph is normalized in the min-max scale so that the zero (the underscore in the lower row) is the minimum, and a # in the higher row is the maximum. so like, _ = lowest key, # = highest key, and everything in between is just vibing on that scale. ⭐

For more information refer to the Latency Monitoring Framework page.

🧚 SEE ALSO

okay that's the whole page bestie, you ate it up. this was 9.0.0, dated 2025-10-21, and yeah, the header/footer said LATENCY-GRAPH(3valkey) — periodt. 💜

📦 where this page comes from