GitHub user git-hulk edited a comment on the discussion: Memory leak and confusing logs
It requires the program binary to inspect the heap profiling. You can use `jeprof --base` to view the memory allocations between two heaps, refer to: https://manpages.debian.org/unstable/libjemalloc-dev/jeprof.1.en.html. After PR #3007 and #3011, we can dump the heap manually at runtime: ```shell ## Enable the memory profiling, set prof_active to true. $ redis-cli> KPROFILE MEMORY ENABLE ## Inspect the profiling status $ redis-cli> KPROFILE MEMORY status ## Dump the profiling file into /tmp directory, which named with `jeprof_` prefix. $ redis-cli> KPROFILE MEMORY DUMP /tmp ## Disable the memory profiling, set prof_active to false. $ redis-cli> KPROFILE MEMORY DISABLE ``` GitHub link: https://github.com/apache/kvrocks/discussions/2984#discussioncomment-13373937 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
