We are testing a server with 128GB
- Filled 30GB of data
- Now Removed data from database, using TTL.
Issue is that, keys are deleted, but the size of redis is 90GB+
# Memory
used_memory:21543685440
used_memory_human:20.06G
used_memory_rss:106070851584
used_memory_rss_human:98.79G
used_memory_peak:31847616096
used_memory_peak_human:29.66G
used_memory_peak_perc:67.65%
used_memory_overhead:853144
used_memory_startup:786512
used_memory_dataset:21542832296
used_memory_dataset_perc:100.00%
total_system_memory:135193665536
total_system_memory_human:125.91G
used_memory_lua:46125941760
used_memory_lua_human:42.96G
maxmemory:52000000000
maxmemory_human:48.43G
maxmemory_policy:volatile-ttl
mem_fragmentation_ratio:4.92
mem_allocator:jemalloc-4.0.3
active_defrag_running:0
lazyfree_pending_objects:0
Even running the instance for about 24 hours, redis is not releasing the memory.
Comment From: antirez
Hello, it does not look like the instance is empty. Please provide more state about your server including the INFO command output and the MEMORY DOCTOR output.
On Fri, Feb 8, 2019 at 12:33 PM Anwesh notifications@github.com wrote:
We are testing a server with 128GB
Filled 30GB of data Now Removed data from database, using TTL.
Issue is that, keys are deleted, but the size of redis is 90GB+
Memory
used_memory:21543685440 used_memory_human:20.06G used_memory_rss:106070851584 used_memory_rss_human:98.79G used_memory_peak:31847616096 used_memory_peak_human:29.66G used_memory_peak_perc:67.65% used_memory_overhead:853144 used_memory_startup:786512 used_memory_dataset:21542832296 used_memory_dataset_perc:100.00% total_system_memory:135193665536 total_system_memory_human:125.91G used_memory_lua:46125941760 used_memory_lua_human:42.96G maxmemory:52000000000 maxmemory_human:48.43G maxmemory_policy:volatile-ttl mem_fragmentation_ratio:4.92 mem_allocator:jemalloc-4.0.3 active_defrag_running:0 lazyfree_pending_objects:0
Even running the instance for about 24 hours, redis is not releasing the memory.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.
-- Salvatore 'antirez' Sanfilippo open source developer - Redis Labs https://redislabs.com
"If a system is to have conceptual integrity, someone must control the concepts." — Fred Brooks, "The Mythical Man-Month", 1975.
Comment From: kanishkablack
127.0.0.1:6380> MEMORY DOCTOR
Sam, I detected a few issues in this Redis instance memory implants:
* High fragmentation: This instance has a memory fragmentation greater than 1.4 (this means that the Resident Set Size of the Redis process is much larger than the sum of the logical allocations Redis performed). This problem is usually due either to a large peak memory (check if there is a peak memory entry above in the report) or may result from a workload that causes the allocator to fragment memory a lot. If the problem is a large peak memory, then there is no issue. Otherwise, make sure you are using the Jemalloc allocator and not the default libc malloc. Note: The currently used allocator is "jemalloc-4.0.3".
I'm here to keep you safe, Sam. I want to help you.