How to figure out the reason for Azure Cache Redis memory usage pattern?

Kaarlo Räihä 5 Reputation points
2023-07-17T06:49:47.61+00:00

We are having a following problem with Azure Cache Redis (basic tier), the memory usage increases steadily and then the evict happens. The issue is that we are not writing any new data to Redis. In total we have eight keys (checked with info keyspace) and the biggest one has about 500 bytes of data in it.

I have attached a log of info memory

info memory

# Memory

used_memory:102750824

used_memory_human:97.99M

used_memory_rss:133332992

used_memory_rss_human:127.16M

used_memory_peak:102936656

used_memory_peak_human:98.17M

used_memory_peak_perc:99.82%

used_memory_overhead:392272

used_memory_startup:289080

used_memory_dataset:102358552

used_memory_dataset_perc:99.90%

used_memory_lua:32768

maxmemory:285000000

maxmemory_reservation:30000000

maxfragmentationmemory_reservation:30000000

maxmemory_desired_reservation:30000000

maxfragmentationmemory_desired_reservation:30000000

maxmemory_human:271.80M

maxmemory_policy:volatile-lru

mem_allocator:jemalloc-4.0.3

azure_redis_memory_increase

Azure Cache for Redis
Azure Cache for Redis
An Azure service that provides access to a secure, dedicated Redis cache, managed by Microsoft.
219 questions
{count} votes

1 answer

Sort by: Most helpful
  1. ShaktiSingh-MSFT 13,826 Reputation points Microsoft Employee
    2023-09-14T04:47:00.9566667+00:00

    Hi Kaarlo Räihä •,

    Thanks for sharing the solution with Q&A community.

    I'm glad that you were able to resolve your issue and thank you for posting your solution so that others experiencing the same thing can easily reference this! Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others ", I'll repost your solution in case you'd like to "Accept " the answer.

    Solution adopted is as below:

    Issue was related to Azure AD login. It was fixed by Microsoft on 5th September 2023.

    Thanks

    0 comments No comments