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

@saper

@gargron

Hey now, surely we can come together and all agree that Unix-style OSes are far better at this than Windows, for which similar situations tend to break down into "where did this memory go and who even requested it? Literally no way to ever tell, I guess just reboot periodically!"

@keithzg @Gargron I am not sure I know enough about Windows memory allocator here.

From what I see this is a remnant from brk()/sbrk()-style memory allocation, which is deeply rooted in UNIX history and memory segmentation.

Paging is clearly more difficult to manage.