Technologies/Redis/redis.commands.usec_per_call
RedisRedisMetric

redis.commands.usec_per_call

Average CPU time per command call
Dimensions:None
Available on:DatadogDatadog (1)Native (1)

Summary

Pre-calculated average execution time per command invocation in microseconds (usec / calls). This derived metric simplifies command performance analysis by providing ready-to-use per-operation latency. Commands with increasing averages over time indicate performance degradation, possibly from dataset growth, inadequate memory, or inefficient access patterns. Compare across commands to identify which operations consume disproportionate server time.

Interface Metrics (2)
DatadogDatadog
Average CPU time per command call
Dimensions:None
Native
Average number of microseconds per call for a specific command
Dimensions:None
Sources
redis.command.usec_per_calldocs.datadoghq.com
redis.commands.usec_per_callredis.io
Related Insights (3)
Serial Execution Masking Redis Cache Effectivenesswarning

Event loop blocking creates false appearance of cache ineffectiveness - Redis cache hits are fast individually, but serial request processing prevents concurrent cache lookups from improving overall throughput during traffic bursts.

▸
AOF Persistence Latency from Synchronous Disk Writeswarning

When AOF persistence is enabled with appendfsync always or everysec, slow disk I/O can cause write latency spikes. redis.persistence.aof_last_rewrite_time_sec increasing significantly indicates AOF file growth without rewrite, amplifying disk I/O overhead.

▸
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.

▸