3 ms·
Going to try this right now! Will report back. OOC, why isn't this part a ruby default? Isn't it always better to be more memory efficient. (I'm trying to unde
by nomilk 3y ago
Going to try this right now! Will report back.
OOC, why isn't this part a ruby default? Isn't it always better to be more memory efficient. (I'm trying to understand what the trade offs are, if any)
EDIT: well, exactly 6 minutes later, I'm done. I followed these instructions: https://elements.heroku.com/buildpacks/gaffneyc/heroku-buildpack-jemalloc https://elements.heroku.com/buildpacks/gaffneyc/heroku-build...
The app seems to work like usual, I'll just have to wait and see what happens to memory use.
I will reply here in 12 hours with a screen shot showing the results (before/after memory use), whatever they may be.
Also, for reference, here's the metrics for the past 24 hours (LOTS of memory problems): https://imgur.com/a/M8IHd5z https://imgur.com/a/M8IHd5z
- bmulholland 3y agoYeah, I had the same reaction last week. It's not a Ruby default because some versions of Linux can't use it. ¯\_(ツ)_/¯
- nomilk 3y agoFor anyone interested, here's the result: https://imgur.com/a/c62gjKQ https://imgur.com/a/c62gjKQ (the red vertical line is the point from which jemalloc was used). It looks like memory usage did indeed go down, and critical errors fell by about 84%.
- nomilk 3y agoFor completeness, here are the metrics a full 24 hours after the change: https://imgur.com/a/lbdzFvN https://imgur.com/a/lbdzFvN