RR 411: What causes Ruby memory bloat? with Hongli Lai

SponsorsSentry use the code “devchat” for 2 months free on Sentry small planTriplebyte offers a $1000 signing bonusRedisGreenCacheflyPanelCharles Max WoodDave KimuraEric BerryJoined by Special Guest: Hongli LaiSummaryEric Berry starts by sharing how Phusion and Phusion passenger changed his career and thanks Hongli Lai for his work. Hongli talks about where Phusion is now and shares what's new with passenger 6. The panel compares passenger and puma and Hongli explains why passenger is the better choice. The panel wonders about deployment strategies and Hongli shares what he has seen done with Passenger.Hongli discusses the article he wrote about memory bloat. He starts by explaining why he wrote the article. The panel discusses what causes memory bloat and how to identify memory bloat versus memory leaks. Hongli explains how the system memory allocator works and why people are using Jemalloc instead. The panel discusses Jemalloc and wonders why Ruby doesn’t adopt Jemalloc. Hongli shares his magic solution for solving the memory bloat problem and other tips for managing memory.Linkshttps://www.phusionpassenger.com/https://github.com/phusion/passenger-dockerhttps://devchat.tv/ruby-rogues/rr-403-rails-needs-active-deployment-with-stefan-wintermeyer/  https://blog.phusion.nl/2019/03/14/what-causes-ruby-memory-bloat/https://www.joyfulbikeshedding.com/blog/2019-03-14-what-causes-ruby-memory-bloat.htmlhttps://www.joyfulbikeshedding.com/blog/2019-03-29-the-status-of-ruby-memory-trimming-and-how-you-can-help-with-testing.htmlhttps://en.wikipedia.org/wiki/Lars_Bak_(computer_programmer)https://twitter.com/honglilaihttps://www.facebook.com/RubyRogueshttps://twitter.com/rubyroguesPicksDave Kimura:LEGO Marvel Super Heroes Avengers: Infinity War The Hulkbuster Smash-Up 76104 Building Kit (375 Piece)