Azure Cache for Redis
An Azure service that provides access to a secure, dedicated Redis cache, managed by Microsoft.
258 questions
What counts as an Operation in Azure Cache for Redis Metrics?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(112.00000000000001, 87%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESW%3C/text%3E%3C/svg%3E)
Shaun Wallace
20
Reputation points Microsoft Employee
I am investigating an issue where the Server Load metric for my Azure Redis Enterprise Cache jumped to 100% for a few hours. I see a corresponding increase in total operations
But its not clear to me exactly what this includes. Does a single LUA script count as 1 operation? Does each call to TIME/HVALS/HDEL/etc count as an operation? Does a client attempting to connect count as an operation?
{count} votes
-
Oury Ba-MSFT 19,501 Reputation points Microsoft Employee2024-08-19T20:07:14.26+00:00 One possibility is a spike in the number of client connections. Establishing new connections is a processor-intensive operation on the Redis server, so it can result in increased server load like this.
Some Redis commands are more expensive to execute than others. The Redis commands documentation shows the time complexity of each command. Redis command processing is single-threaded. Any command that takes a long time to run can block all others that come after it.
Server Load should stay below 80% in normal operations, to allow some headroom for maintenance events that will periodically impact the cache and require some additional processing power.
-
Shaun Wallace 20 Reputation points Microsoft Employee
2024-08-19T23:22:22.4033333+00:00 To clarify, each call to those commands counts as 1 "Operation" in the metrics? And nothing else except for calls to those commands count as operations?
Is there a way to get a more detailed breakdown of what commands / operations are being executed on the server? Ideally some sort of summary like AUTH: 100 HVAL: 2000 HDEL:100 etc...
In my case the connected clients is flat until the server load jumps to 100%, after which it drops, I assume to clients being kicked out due to the high load.
On my client side optics I do see an increase in load around this time, but the load increase Im seeing on the redis server increases more than I would expected based on my client side load. There could easily be a bug on my side, but it is difficult to investigate without more detailed metrics.
Sign in to comment
Sign in to answer