Good memory allocator for data processing

Carlos O'Donell carlos@redhat.com
Wed May 6 18:41:32 GMT 2020


On 5/6/20 2:30 PM, Carlos O'Donell wrote:
> On 5/3/20 10:50 PM, Yubin Ruan wrote:
>> Thanks for the information, but does it provide any configuration
>> method, I mean, never return, instead of
>>
>>         "However, if the top chunk in a heap - the portion adjacent to
>> unmapped memory - becomes large enough, some of that memory may be
>> unmapped and returned to the operating system"
> 
> Yes, see the glibc.malloc.mmap_max and glibc.malloc.trim_threshold.
> 
> You want to raise the mmap max so mmap is never used for single

Should say "lower the mmap max" since this is a count of the number
of mmap's to have in use, and if you set it to 0 then you won't use
any mmap's to service large allocations. This may lead to fragmentation
issues.

-- 
Cheers,
Carlos.



More information about the Libc-help mailing list