0

fairly new to Redis and working on a Azure Cache for Redis implementation.

In the Azure documentation around Redis trouble shooting it's stated that there can be long-running commands and that the redis command documentation shows the time complexity of all commands.

I couldn't find anything around the config set maxmemory-policy command.

Is my assumption correct that setting/changing the maxmemory-policy itself is not an expensive command (unlike e.g. resharding/rebalancing a cluster)?

(I know, "expensive" does not really have a proper definition here :) )

Thanks for any hints or answers!

Sebastian
  • 1,743
  • 1
  • 16
  • 35

1 Answers1

1

Yes, the config set command itself is not an expensive command. It iterates the config array which contains about 200 items, to find the config, and set it. That's all.

However, after the setting, Redis might need to free memory for evicted items periodically or for each command. That's a cost.

for_stack
  • 21,012
  • 4
  • 35
  • 48
  • thanks! That additional cost I would attribute to the functionality of the requested memory-policy, but good to mention it! – Sebastian Jun 17 '21 at 10:09