Annual reminder to use jemalloc with your Ruby/Rails apps in production! You don't need to change your app and it will use less memory and perform better

5
Share
Share on Mastodon
Share on Twitter
Share on Facebook
Share on Linkedin
Drew 🐘

@tenderlove And if you can't use jemalloc tune your glibc memory arenas!

0
12mo
Damax

@tenderlove Thanks for the reminder. I was updating my stack the following week and jemalloc as being shipped! It works well. Ruby 3.1 and 3.2 also helped a lot.

0
11mo
Leon Berenschot

@tenderlove thanx for your reminder, exited for the savings it will give in the long run. I own you a drink ;)

0
11mo
Jyrki :jyrki:🐾:heart_nb:

@tenderlove wild what swapping out what seems to be a core functionality of any OS can do. seeing some immediate effects already 12 hours in!

grafana panels showing some memory usage of a Rails application for the last three days. there are three noticeable dives in usage whenever the app restarted, before jemalloc the used memory grew quite rapidly, with the last restart where jemalloc was enabled it doesn’t consume all the memory 12 hours in.
0
10mo
Eike :blobcatverified:

@tenderlove honest whataboitism: what about malloctrim? Fullstaq ruby has that as an option and it seems to do more or less the same thing? Do you have an opinion on that?

1
10mo
Replies