keithzg is a user on mastodon.club. You can follow them or interact with them if you have an account anywhere in the fediverse. If you don't, you can sign up here.

@gargron The answer is "using Ruby", obviously!

(sorry)

@keithzg The answer is malloc's overallocation default due to RedHat's preferences and malloc's failure to return free empty heaps as a performance precaution

This is why you don't get memory issues when using jemalloc instead of glibc's malloc

keithzg @keithzg

@gargron Yeah to be honest I did read through it and found it very interesting, especially how apparently patching a malloc_trim() call into Ruby 2.6 actually *improved performance* in addition to reducing memory consumption.

Also very interesting, as you point out, is the somewhat warping influence Red Hat has on the default state and configuration of the underlying software stack.