Re:Fixing a Tough Memory Leak in Python
by masklinn on Saturday December 08, 2018 @09:05AM
(#18635245)
> I'd say it's a problem in the interaction of that specific version of python with that specific malloc. From a performance perspective we could not afford to simply force malloc to only use mmap for every small allocation (as it would thrash the TLB and/or balloon memory usage).
And other option might have been to switch to a malloc using mmap'ed size-class arenas like jemalloc or somesuch?
And other option might have been to switch to a malloc using mmap'ed size-class arenas like jemalloc or somesuch?