RedisMetricredis.commands.usec
Total CPU time consumed by a specific commandDimensions:None
Available on:Native (1)
Summary
Total cumulative microseconds spent executing a specific Redis command since server startup. Dividing this by the command call count yields average execution time per command invocation. Rising values relative to call count indicate increasing per-command latency, often due to growing dataset sizes, memory pressure forcing disk I/O, or CPU contention from other expensive operations.
Interface Metrics (1)
Sources
Related Insights (1)
Command Latency Spikes from Expensive O(N) Operationswarning
Certain Redis commands have O(N) complexity (KEYS, SMEMBERS, HGETALL, LRANGE without limit) and can cause latency spikes when executed on large data structures. redis.commands.usec tracking per command identifies hot spots.
▸