New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
high mem_fragmentation_ratio #7741
Comments
@lw5885799 We currently have limited visibility into the internals of libc malloc (a lot more details when using jemalloc). |
@oranagra is there any reference to analyze the proc//smaps. I know few about this memory log. I mean how to find the cause of high mem_fragmentation_ratio by the smaps log. |
just see which mapping consumes the majority of RSS and if you can conclude that's the libc allocator heap or not. maybe you'll be able to prove that it's related to some other library that got loaded, or maybe that's a memory mapped file. if that's the allocator then you need to find a way to look into it's internals. btw, why not use jemalloc? |
Thanks. I will try this. That guy who building the cluster accidently changed the allocator in product environment. We have changed allocator to jemalloc. Still, want to know what happened |
I use the My old cluster with malloc had a used_memory_rss 5.5GB used_memory_peak 4.9GB and used_memory 39MB. The mem_fragmentation_ratio reached to 143. Is it still a normal thing? |
if the rss matches the peak memory, it could just be fragmentation, or some issue with the allcator. it's hard to tell for sure because we don't have a lot of info with libc allocator. |
version: 5.0.2
problem: high mem_fragmentation_ratio
info memory:
used_memory_human: 24.69M
used_memory_rss_human: 236.4M
mem_fragmentation_ratio: 9.59
mem_allocator: libc
I checked some article. Usually, the mem_fragmentation_ratio is between (1- 1.6). I have no idea why it happenned.
how can I get log or other way to find the cause?
The text was updated successfully, but these errors were encountered: