jemalloc coring in je_bitmap_set
Paul.Marquess at owmobility.com
Wed Aug 19 13:38:28 PDT 2015
> From: jemalloc-discuss-bounces at canonware.com [mailto:jemalloc-discuss-bounces at canonware.com] On Behalf Of Daniel Micay
> On 18/08/15 05:58 PM, Paul Marquess wrote:
> >>> Do you have any feeling whether it is safe to have jemalloc and THP at the same time?
> >> I've had pretty poor experience with the mixture even within the past month. The problem is that at some point (under a day of intermittent benchmarking in all the cases I observed) the kernel gets into a fragmented memory state that it cannot recover from without a reboot, and the only obvious indications are decreased performance and increased page faults.
> > Do you think that disabling madvise with opt.lg_dirty_mult:-1 allows jemalloc & THP to co-exist without causing other unwanted side-effects?
> > Paul
> Well, you won't lose huge pages if you've disabled purging. It's going to increase memory usage but that may not be a problem for you.
Thanks Daniel, that's what I was expecting. Just checking if anyone has encountered any nasty surprises (like a hit on performance) with the workaround to get jemalloc & THP to play together.
More information about the jemalloc-discuss