On Thu, 2 May 2019 at 05:02, Mark Nelson <mnelson@xxxxxxxxxx> wrote: [...] > FWIW, if you still have an OSD up with tcmalloc, it's probably worth > looking at the heap stats to see how much memory tcmalloc thinks it's > allocated vs how much RSS memory is being used by the process. It's > quite possible that there is memory that has been unmapped but that the > kernel can't (or has decided not yet to) reclaim. > Transparent huge pages can potentially have an effect here both with tcmalloc and with > jemalloc so it's not certain that switching the allocator will fix it entirely. Most likely wrong. -- Default kernel's settings in regards of THP are "madvise". None of tcmalloc or jemalloc would madvise() to make it happen. With fresh enough jemalloc you could have it, but it needs special malloc.conf'ing. > First I would just get the heap stats and then after that I would be > very curious if disabling transparent huge pages helps. Alternately, > it's always possible it's a memory leak. :D RedHat can do better (hopefully). ;-P -- End of message. Next message? _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |